IT Consultant Everyday Notes

Just some problems/solutions storage

Monthly Archives: September 2012

Tip: Server 2012/Windows 8–How to logoff

In Server 2012/Windows 8 Microsoft changed “traditional” logoff way… Now, to logoff go to the Start page, click on your user account picture and select "Sign out".

Server 2012: Cannot install Hyper-V role

Here is a problem without resolution so far:

I have a Microsoft Hyper-V 2008 R2 server in my lab. Now, when ewe have Server 2012 RTMed I decided to upgrade my infrastructure to Microsoft Hyper-V 2012.

Unfortunately it is NOT SUPPORTED. So I had no other choice than rebuild the host.

I rebuilt the host with Microsoft Hyper-V 2012 Server but the server never booted to OS properly (I mean the first boot after installation)

I tried to install a Windows Server 2012 Std. It was installed successfully and booted, but as soon as I enabled Hyper-V role the server asked for reboot and hung in starting state Sad smile

I checked hardware prerequisites – everything look good. And I do not think we have much changed from 2008 R2…

 

So I rolled back to Microsoft Hyper-V 2008 R2 Server at this point and trying to find what it could be.

If anybody bumped to the same issue and know how to resolve it please let me know.

Linux and Unix Clients for SCCM 2012 SP1

The following UNIX and Linux versions are supported in the Beta release.

  • AIX Version 7.1 (Power)
  • AIX Version 6.1 (Power)
  • AIX Version 5.3 (Power)
  • HP-UX Version 11iv3 (IA64 & PA-RISC)
  • HP-UX Version 11iv2 (IA64 & PA-RISC)
  • RHEL Version 6 (x86 & x64)
  • RHEL Version 5 (x86 & x64)
  • RHEL Version 4 (x86 & x64)
  • Solaris Version 10 (x86 & SPARC)
  • Solaris Version 9 (SPARC)
  • SLES Version 11 (x86 & x64)
  • SLES Version 10 SP1 (x86 & x64)
  • SLES Version 9 (x86)

The Clients can be downloaded from here

This blog post describes how to install them.

Server 2012: Remote Server Administration Tool for Windows 8 is available now

SCCM 2012: Application cannot be installed from Task Sequence

Microsoft introduced new type of SCCM resources – Applications in addition to existed before Packages.

Problem: I created an OSD TS and add Install Application step. When I tried to start the TS deployment it failed. If I replace Install Application step to Install Package (and create a Package for the same software) everything works fine. I also can deploy TS without Install Application step.

Resolution: Strange enough, but it works if  the Application Deployment type is configured to “Download content from Distribution point and run locally” even though this is a settings for slow and unreliable network! And my client is on the same 1GB network with the DP. Anyway, it works.

image

people  here also mentioned it can be fixed if Distribution Points are grouped and content is assign to the DP Group, not to DPs. Sounds equally strange, I did not test that.

Windows 7: How to allow users to install printers if they are not Administrators

Problem: If users are not Local Administrators they cannot install Printer (and other) drivers to their machines.

Resolution:

There are two main approaches:

1. Pre-stage drivers for users using ConfigMgr or PNPUTIL as described here: http://blog.coretech.dk/mip/personal-note-no-5-make-driver-available-for-none-admin-user/ and here: http://technet.microsoft.com/en-us/library/cc772036.aspx

2. Or allow installation of a specific hardware class for limited users as described here: http://technet.microsoft.com/en-us/library/cc725772(v=ws.10).aspx

3. Use GPO as described here: http://techibee.com/group-policies/allow-normaldomain-users-to-add-network-printers-in-windows-7/457 . Just in case the link will be dead – it is under Computer Configuration – Administrative Templates – Printers – Point and Print Restriction

Windows 7: Internet Connection detection

Problem: If you use a proxy to connect to Internet you may see an annoying exclamation point on your Network connection icon in Task bar.

Basically it says you do not have Internet connection. 

The matter in fact Windows 7 tries to

1. Resolve FQDN of www.msftncsi.com. It should be resolved into 131.107.255.255

2. sends HTTP request to get a plain text file at URL: http://www.msftncsi.com/ncsi.txt

This technique is called Network Connectivity Status Indicator(NCSI) service and was introduced in Vista. It is described here.

Wireshark shows that NCSI goes directly to MS site (bypassing proxy) even though proxy is properly set in Internet Explorer.

Resolution: Kyle pointed to an NETSH command to force NCSI use proxy:

netsh winhttp set proxy <your_proxy:port>

you can verify settings using

netsh winhttp show proxy

After that on Wireshark trace you see traffic from NCSI goes to proxy and preperly replied. Indication in task bar is ok.