IEEE 802.1X authentication protocol support for WinPE

Microsoft has released hotfixes that now add 802.1x support to both WinPE 2.1 and WinPE 3.0. Here are the links to the hotfixes.

WinPE 2.1: http://support.microsoft.com/kb/975483

WinPE 3.0 (Windows 7 & Server 2008 R2): http://support.microsoft.com/kb/972831

Step by Step Instructions to Inject the update using DISM.

1) Once you have downloaded the update, extract the files to your deployment server. In this example, I created a folder on my E:\ called 802PE.

2) Mount the LiteTouchPE_x86.wim using DISM: DISM /Mount-WIM /WIMFile:E:\DeploymentShare$\Boot\LiteTouchPE_x86.WIM /index:1 /MountDir:E:\Mount

3) Inject the package: DISM /Image:E:\Mount /LogPath:AddPackage.log /Add-Package /PackagePath:E:\802PE\Windows6.1-KB972831-x86.cab

4) Unmount and Commit your changes: DISM /Unmount-WIM /Commit /MountDir:E:\Mount
5) As an additional step you can validate the package was installed successfully: DISM /Image:E:\Mount /Get-Packages (Note: When you add the package in step 3 it should tell you, “The operation completed successfully” if the package injected with no errors.)

Configuring Default User Settings – Full Update for Windows 7 and Windows Server 2008 R2

I’ve received some emails in my inbox lately about configuring Windows 7 Default User Settings on the Core Image. Instead of re-inventing the wheel, check out this blog posted by Michael Murgolo from the DeploymentGuys.

http://blogs.technet.com/deploymentguys/archive/2009/10/29/configuring-default-user-settings-full-update-for-windows-7-and-windows-server-2008-r2.aspx

Windows 7 Deployment Useful Tip # 2 – Enabling the Standard User to delete Desktop Shortcuts from C:\Users\Public\Desktop

For thought, it is a general rule, set expectations with rationalization. If your environment consists of users running as administrators on their machines, this is something you really want to try and get away from.  Maintaining a well managed PC in the corporate environment goes out the Windows if you don’t lock and secure your systems. Destabilization of the desktop causes additional work for everyone, not to mention productivity down time for everyone.

User Account Control works by protecting access to administrative rights, and this involves elevation of privilege. One small challenge I came across recently was giving Standard Users the ability to delete desktop icons that are created during the installation of applications. Specifically, desktop icons stored in C:\Users\Public\Desktop. This happens because desktop icons were installed/created by a trusted install account (e.g. Administrator). Since the user is not the owner of the file, they cannot take ownership of the file. When a user attempts to delete a desktop shortcut, Windows 7 requests some kind of consent or credential to do so. Unfortunately, UAC won’t allow the standard user to execute this task.

The recommended solution would be creating a script to run against the desktop folder to modify the ACLs during post installation of the OS. Alternatively, you can add the following commands to your Task Sequence in StateRestore.

attrib -h c:\Users\Public\Desktop

Icacls c:\Users\Public\Desktop /grant “TEST.com\Domain Users”:M /T

attrib +h c:\Users\Public\Desktop

Remember to replace “TEST.com with the name of your domain. Also note, the reason for the attrib requirement is because the public desktop folder is hidden. In Windows 7 the public desktop is a reparse point of the folder known as desktop. Credit goes to Josh Brungardt,  my colleague, for countless testing scenarios to get this to work.

Cheers,

Rich

MSIEXEC and application uninstall tip

I was inspired to write this post when a colleague of mine approached me today asking how to uninstall a previous version of an MSI and install a newer version. While this doesn’t directly tie int to OS Deployments, the need to uninstall & reinstall applications deployed on the estate is a very common task amongst Enterprise Solutions Administrators. Unfortunately, there isn’t a single command you can run from MSIEXEC which will find and destroy all older versions of an application. To do this, it would require the use of WISE packaging studio, or some other app packaging program.

One of the easiest methods for uninstalling an MSI is to use the /x command. Here is an example below.

msiexec /x “c:\vmtools\VMware Tools.msi” /qn /norestart /log c:\toolsUnInstall.log

However, what if you find yourself in the scenario where you don’t have the MSI of the older version you’re trying to uninstall. Luckily, that information can be found in the REGISTRY.

The information can be found at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\

There should be the product ID there as well as a direct command you can run to uninstall the software.

Cheers,

Rich

Folder Redirection Policy for Windows 7

Raise your hand if you’re using Windows XP in your corporate environment and make use of a VPN client to connect back to your network resources when you’re off campus. Does your company leverage any type of manual folder redirection for your My Documents folder to point to a network location? If so, how many of you struggle with accessing your home directory (e.g. My Documents) when you’re working away from the office. This is a very common complaint amongst the information worker. The issue is, when you go home, logon to your laptop, connect to the VPN, and click on your My Documents, you don’t have access to your data. My wife complains to me, “Why can’t I access my home drive?!” This is because when you logon to your machine, you’re not connected to the corporate network. A workaround is either knowing the UNC on the network you can browse to access your data. While this can be annoying for some, but an annoyance anyway, there are solutions out there that can help.

My first piece of advice is to eliminate the use of the VPN client altogether. There are technologies out there that can provide a more , Cisco’s AnyConnect or Microsoft’s Direct Access solution. Depending on customer requirements, you’ll need to examine the clientessVPN solutions that are out on the market.

As part of your Windows 7 Deployment Project, you may consider leveraging group policies to create a more secure and managed desktop environment. Folder redirection is one of the policies you might want to consider. Generally speaking most organizations have a User Data Policy, which dictates where user data should be stored. In the corporate environment it is a very good idea to backup user data to a network location such as  SharePoint, Network Share, Home Directory, etc. Alternatively, the use of external devices such as USB, external hard disk, etc. can be used. Folder redirection policy is a great way to ensure that as a user logs on, their documents are pointed to a network location.

When creating a new User Account in Active Directory Users & Computers (ADUC), you have the ability to create a Home Folder to point to a network location. One of the most common scenarios is to map a Drive Letter to point to a specific UNC on a filer where you would like to store the user’s My Documents folder.

Additionally, if your intention is to implement Windows RE into your deployment solution, Documents Folder Redirection is a critical piece of the ability to self restore a PC. If the user’s primary source data is not kept on a Network Share, when the System Image Restore process is initiated, there is some potential for the loss of all local data.

Configuring Folder Redirection Policy in Windows 7

Step by Step

1)      In the GPMC, right-click the OU on which you want to apply Folder Redirection (at the time of this writing the policy is configured on Test OU – Test – Users) , and choose “Create a GPO in this domain, and Link it here.”

2)      Name the GPO, say, “Win 7 Documents Folder Redirection”

3)      Right-click on the policy and choose Edit.

4)      Drill down to Folder Redirection: Select User Configuration – Policies – Windows Settings – Folder Redirection

5)      Go to the Documents folder, right-click and choose Properties.

6)      On the Target tab make the Setting set to Basic – Redirect everyone’s folder to the same location.

7)      The Target folder location is set to Redirect to the following location

8)      The Root Path is set to %HomeShare%\My Documents

9)      Click Apply

Enjoy!

Rich

Windows 7 Deployment Useful Tip # 1 – Creating Read-only partitions during deployment with MDT 2010

Depending on your organization’s security policy, you may have the need to make a partition read-only. I have been working on a solution for the last 4 weeks to implement Windows RE into the build process with MDT 2010. Because of security requirements, this drives needs to be marked as read-only.

In MDT 2010 Task Sequence, you can do this by configuring two command lines during State Restore.

Task Sequence steps were created to run CACLS command line to make R: drive Read-Only for “Authenticated Users”.

ECHO Y| CACLS R:\ /S:O:BAG:SYD:PAI(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)

cacls R: /E /R “Authenticated Users”

OSD: List of WMIC Results for various Makes & Models of machines

One of the most comprehensive lists for various Makes & Models of machines using the WMIC query.

http://www.faqshop.com/configmgr2007/default.htm?http://www.faqshop.com/configmgr2007/admin/aosd/list%20wmic%20results.htm

Highlight Tip with Trace32.exe

I was working with Scott Culbertson (MCS) today troubleshooting a custom process to install HP hardware based drivers using the SSM.EXE tool. He shared a useful tip when using Trace32.exe. We were parsing through the SMSTS.log looking for validation on some specific conditions set in the task sequence. In this particular case there was an entire Group in State Restore that was being skipped completely. One useful thing you can do with Trace32.exe is Highlight the specific error you’re searching for. This is particularly helpful when searching through lengthy log files looking for a specific error or step in the TS.

Open Trace32.exe and go to Highlight. From there you can enter the string to search for and all lines containing the text will be highlighted.

Simple, but useful tip.

Unattend.XML, Windows 7 Deployments, and PC naming

You may experienced an error when installing Windows 7, “Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [specailize]. The answer file is invalid.”

There could be several reasons for this error and the best place to start looking is in the Windows Setup log file in C:\Windows\Panther. In this case, I found the following error in the setup log.

<ComputerName>MENDTVMware-50 0e 64 8d bd df 91 77-98 ee 3b a4 bb 58 7b b4</ComputerName>

Windows has a limit of 15 characters for the computer name. To resolve this issue, you may want to reconsider your PC naming convention strategy in your organization.

Adding Network Printers as a Standard User in Windows 7

If your environment consists of users that are local admins on the machine, this is something you should really try to get away from. Running in full administrative mode in a Windows environment is probably one of the most dangerous things that can be done from an security standpoint. One of the luxury’s of User Account Control is that it allows you to elevate privileges when needed. One of the many advantages of deploying Windows 7 is that standard users can do more then what they could do previously with Windows XP. A very common computing task for the everyday worker is installing a Network Printers. I don’t know about you, but, the last thing I want to have to do is call the IT Service Desk to assist me with this effort. Ugh!

In Windows 7, as a standard user, you’re not able to do this without making a few changes to the supporting infrastructure first. There is a computer policy you can deploy to Win7 clients in your environment.

Step by Step

1. In the GPMC, right-click the OU on which you want to apply the Windows 7 Printer Policy, and choose “Create a GPO in this domain, and link it here.”
2. Name the GPO something appropriate, “Windows 7 Printers”
3. Right-click on the new GPO, and choose Edit from the shortcut menu to open the Group Policy Management Editor.
4. Drill down to Printers by choosing Computer Configuration_Policies_Administrative Templates: Policy definition. Click Printers and double click on Point and Print Restrictions.
5. Enable the Policy
6. Disable the “Users can only point and print to these servers”
7. Enable the “Users can only point and print to machines in their forest”
8. Do not show warning or elevation prompt for both “When installing drivers for a new connection” and “When updating drivers for an existing connection.”

Here is a snippet of the Computer Configuration Policy:

Note: If you want to restrict this policy specifically for Windows 7 machines, use the following WMI filter:

Query looks like this: “Select * from WIN32_OperatingSystem where Version=’6.1.7600″ and ProductType=1″