Category Archive: Windows

May 27

Windows 7 setup debugging and disconnect on first boot?

I’ve been troubleshooting an issue with Windows 7 setup on a specific hardware model in MDT with a hodge-podge of a particular vendor’s drivers in the driver store, and I ran into a little issue with Windows 7 setup debugging that I thought I’d share – it doesn’t seem to work right on the first try.  It will connect, then almost immediately disconnect the remote debugger.  If you simply leave the debugger running and attached (in my case, to COM1) and restart the debuggee, it reconnects properly the second time.

I still have no idea why this happens or why it’s so reproducible, but I thought I’d share.  Oh, if you want to do debugging during setup, simply press F8 before the splash screen and select the debugging option from the Advanced Boot Options menu, similar to what you can do in a full Win7 install.

Permanent link to this article:

Mar 12

Windows 7 SP1 language packs and MDT 2010 giving errors?

Seems like Microsoft changed the name of the Language Packs from “Microsoft-Windows-Client-LanguagePack-Package” to “Microsoft-Windows-Client-Refresh-LanguagePack-Package”.  A small distinction, but huge when MDT or SCCM can’t find the language pack name!  In MDT, go to the DeploymentShare’s \Scripts folder, edit “Deploywiz_Initialization.vbs”, and go down to line 1101 – you’ll see that LPQuery is set to look for only the old Language Pack package name.  Add the new package name, and things will work again (you will have to update any media you’ve created, of course).

I found this while searching TechNet, here:

The change should have line 1101 looking like this when you’re done:
LPQuery = “PackageType = ‘LanguagePack’ and (ProductName = ‘Microsoft-Windows-Client-LanguagePack-Package’ or ProductName = ‘Microsoft-Windows-Client-Refresh-LanguagePack-Package’) and substring(ProductVersion,1,7) = ‘” & left(ImgBuild,7) & “‘ and substring(ProductVersion,5,4) >= ‘” & mid(ImgBuild,5,4) & “‘”

Permanent link to this article:

Nov 15

Disk2VHD, XP, and Hyper-V – problems installing Integration Components

After taking a Disk2VHD image of an XP SP3 machine, I noticed that I could not install the Integration Components after copying the VHD to my Hyper-V machine and running the Integration Components setup off vmguest.iso.  It would attempt to upgrade the HAL, tell me I needed to reboot to upgrade the HAL, and then reboot and get to the same place.  If I clicked “OK” again to upgrade the HAL, it would reboot – if I hit “cancel”, the installation would fail.

After some fiddling, I figured out that Disk2VHD added the /HAL=halacpi.dll string to boot.ini for the default boot option, whereas the Integration Components setup was trying to upgrade the HAL to an APIC hal (halaacpi.dll).  I changed the boot option in boot.ini to remove the /KERNEL=ntkrpuni.exe string, changed the /HAL=halacpi.dll string to /HAL=halaacpi.dll, and copied halaacpi.dll from on my XP SP3 media to %windir%\system32.  Once I rebooted, the IC’s installed successfully.  I then went back and removed the /HAL switch from boot.ini entirely and rebooted, and all is well.

Permanent link to this article:

Sep 04

MS10-049 (980436) + wininet application == potential problems with older web servers

Seems like there are some wininet issues with the latest schannel update for Windows XP.  If you’ve got an older web server that is not compliant with IETF RFC 5746, and you use applications that connect to that old web server via wininet (like WCF apps, IE, etc), you are going to have issues.  Microsoft has posted KB 2384778 on how to work around this, so I thought I’d save some people some time if they start seeing this.

Permanent link to this article:

Jul 29

Internet Explorer 8 uninstalls itself if setup is run a second time?

I’ve stumbled across a rather odd issue where users were starting to complain that all of the sudden they were running a previous version of IE again, even though IE8 had been installed previously in the environment.  Also, they were complaining that when starting IE, it would simply close right after the UI was displayed.  In troubleshooting the issue, we went back and looked at the IE8*.log files and found out that IE8’s setup had been run twice on these machines for some reason (still haven’t figured out why yet – that’s for another day), and had uninstalled IE8 during the second run of the installer!

Permanent link to this article:

Jun 17

PageFile vbs for Vista/Win7 systems (may work on XP/2003, not tested)

Wrote up a very small vbscript to handle paging file creation/deletion/modification on Vista/Win7 systems (as PageFileConfig.vbs doesn’t exist inbox, and it didn’t have the ability to handle some of the situations that can arise during setup), and it ended up morphing into this.  Figured I’d save someone the time if they had a need for it, so here it is:

Permanent link to this article:

May 24

SCCM 2007 client certificate issues with 2008 R2 CA

Microsoft supports running SCCM 2007 SP2 on a 2008 R2 server, but I’m doubting whether or not running SCCM 2007 SP2 in Native mode in an environment using a 2008 R2 CA is supported (and if so, there’s an issue to be aware of).  Specifically, it seems like client certificates created with a 2008 R2 CA (following the instructions on Technet for a 2008 CA) do not work by default in SCCM 2007 when running a site in Native mode (you’ll get MP errors stating that it cannot connect via HTTP, and mpcontrol.log will contain errors that the SAN2 fields have errors).  It seems if you create your 2008 R2 CA with the default Key store provider, the client certificates just do not work.  However, if you create your 2008 R2 CA with the Microsoft Strong cryptography provider (which is the default for 2003 and 2008 CAs), magically the certs created work fine.  If you look at the contents of the certs created between a 2008 and 2008 R2 CA, they “look” identical, but something else must be happening I haven’t dug into yet.

Permanent link to this article:

Apr 09

Windows Server 2008 Storage Server default Administrator password

I finally got around to downloading Storage Server 2008 for some hyper-v / iscsi tests I am working on, and after installing Storage Server it did not ask for me to create a password like other Server 2008 / Server 2008 R2 server installs do on first boot.  It appears the default password is “wSS2008!” (minus the quotes, of course).  I found it from a bing search, here.  I figured maybe someone else will run across it and read this, and not have to resort to using DaRT to reset the password offline as I did.

Obviously, if you’re using SS 2008, you’ll want to change this password anyway – not sure why this was done this way, but it was.

Permanent link to this article:

Apr 07

KB974417 installation failure

OK, ran across this today, and there are a few ways to fix it.  The most time-consuming way (but seems to me to be the least invasive) is to remove 976569 and 976570, install 974417 (reboot), and then re-install 976569 and 976570.  I do not know what it is about those two updates that seems to cause the failure, but since I’m building images I don’t really care either – the workaround “fixes” it well enough for me.

Permanent link to this article:

Dec 26

Computer Info VBScript

EDIT 9th January 2010 – the script has gone a fairly major revision due to changes in the Office 2010 product key storage location, as well as migrating this to a class-based script for speed.

Again, another side project – a computer info VBScript. I’ve modified it a bit to output information to screen (execute with cscript from a cmd prompt), but this could be modified to do a lot more. This is just a simple script template, and as usual I’m posting here for consumption in the event anyone finds this useful:

Permanent link to this article:

Older posts «

» Newer posts

Bad Behavior has blocked 1042 access attempts in the last 7 days.