Roaming Profiles: From Windows XP to Vista / Windows 7

Quick, short post today, but this will probably save you a lot of time searching for a pretty much non-existent answer to a new “feature” introduced in roaming profiles for Windows Vista and Windows 7. It cost me an hour to figure this out. Hopefully you’ll see this and solve the issue in a jiffy…

You join your brand new Vista or Win7 machines to a your domain and then try logging in with a roaming user account and get a popup notification error saying that Windows has logged you in with a temporary profile. You look in the event viewer and see the following:

All the permissions are set correctly for the share and folders for the roaming profile and the user can create files in the roaming profile folder, but the stupid “Access Denied” error message is still there.

Your roaming profile path MUST have a trailing slash at the end now… Likewise:

What the hell, Microsoft? All along you’re lax (*nix had this enforced all along) and now you change it. At least let us know? Please and thank you…

On a slightly different note, I also suggest that you set the following Group Policies to make your sysadmin life easier:
Computer Config\Policies\Administrative Templates\System\Logon --> Always wait for network at computer startup and logon [Enabled]
Computer Config\Policies\Administrative Templates\System\User Profiles --> Add the Administrators security group to the roaming user profile share [Enabled]
Computer Config\Policies\Administrative Templates\System\User Profiles --> Wait for remote user profile --> [Enabled]

As usual, cheers.

“Slipstream” Adobe Acrobat Pro Updates

Seems like one of those really annoying things out there is deploying an installation of Adobe Acrobat Pro with all (or most) of the updates at once. Of course, this pertains to the Windows version. After doing some intense research and looking through the bits and pieces if suggestions that are out there, I found a much easier way to integrate all the updates into one package.

This one is tricky, you can’t just use the traditional method of running msiexec with the /p parameter and patch over the MSI. What makes it worse is that certain updates can’t be slip streamed or they will prevent future updates from being applied. One can only imagine the headaches that can come out of trying to deploy this without having to install the numerous patches after.

Read more

Clean Installation w/ Windows Upgrade Keys

Smile 🙂

You can use an Vista or Windows 7 upgrade key to do a clean install of their respective operating systems.

How? Do a clean install of Windows. Then run the installer (from the DVD) inside the unactivated copy of Windows you just installed to “upgrade”. Your installation is now marked as an upgrade and you can activate Windows with your upgrade key. Make sure you pick the same version of Windows & architecture (x86 vs x64) you are licensed for both times.

What this means for you? You never have to pay full price for Windows, unless of course, if you can’t wait for the second install.

Additional tip: Create a bootable USB flash drive (at least 4GB) from the installation DVD and use that instead. Each install can then be done in about 10-15 minutes since it’s not using the optical media.



EDIT: Update with an alternative method (seems to be more reliable to me).

    Install Windows as described above (the first time).
    Open the registry editor and change the “MediaBootInstall” DWORD value in HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE\ from 1 to 0.
    Open an administrative command prompt and run the command “slmgr/rearm”.
    Reboot, then enter your key from the Computer Properties and activate.