ifM63x64.sys file missing or corrupt - SCCM OSD (X1 Carbon)

Building a new Lenovo X1 Carbon with the new integrated LAN adapter (no more guessing which USB port to use!) via SCCM 2007 and I came across this little blinder.

After the first reboot to OS I was presented with this error screen:

I spotted that is was driver in my driver pack (taken from Lenovo's SCCM pack) for the  Intel Ethernet FCoE Virtual Storport Miniport Driver.

I located the driver in my driver pack and removed it - left he check box UNTICKED to update the distribution point and then manually when and updated it after myself. 

Once I was happy that the source had incremented by one version I kicked off the build again.

Sure enough it sailed through and we are all happy....

 

Operating System Deployment with USB Dongles (Lenovo in my case)

With the advances in technology we have seen in recent years, devices have become smaller, thinner and lighter than ever before.

With this we are finding that some devices are loosing functionality - ie. Some devices are having ports omitted to retain their slender profile.

The Lenovo X1 Carbon adopted this approach and required a USB dongle which I posted about the pitfalls of PXE boot here: Lenovo X1 PXE Issues

I've seen an increase in the issues these dongles are causing us deployment techs, one of those being that each of these dongles have their own MAC address.  In true tech style when we see this new wizardry the first thing we say is "MINE"... Well actually the first thing we normally say is "Ooh Shiney" but then there's a Smeagle like "My Precious" when we claim the Shiney as our own.

I did this.  I had my very own dongle.  It worked great.  ONCE!  Every subsequent build failed.  I did a bit of research and found that it had it's own MAC that was registering in SCCM so I had to surrender my Shiney and give it on to the user.

I now use the supplied dongles for each build as it isn't worth the trouble but I have it on good authority that with the latest gen of Lenovo kit they are shipping certain models with on-board NICs (therefore unique MACs) and the dongle is purely a port extender utilising USB to present an Ethernet port.

If you have fallen prey to this (and insist on using one dongle to rule them all) you need to read my earlier post to search SCCM for machines by their MAC address.

Have fun...

DocN

HP DC7800 will not boot from USB Boot Pen

First model I came across in the roll out was a HP DC7800.  My first task was to deploy our Windows 7 image and then check which drivers were missing.

I came to boot from USB by pressing F9 to get to the boot menu and choosing "USB"

My pen fired up and flickered away whiles loading the initial boot file.  The progress bar galloped across the screen like a trusty steed on Derby Day until it reached the end and froze.

3 pens and 2 machines later I discovered there is a BIOS setting under security that required disabling:  Data Execution Prevention.

As soon as this was disabled, subsequent boots worked like a charm.

The Dells... THE DELLS !!!

So phase 2 of our Windows 7 deployment begins next week.  We have approx 1000 machines we are visiting with a raft of memory to upgrade to 4GB and give a new lease of life in the form of my Windows 7 Image.

Up until last week the entire non-Lenovo estate was to replaced.  Today I've been told all:

Dell 755
Dell 760
Dell 780
Dell 790

HP DC7800
HP DC7900
HP 6000
HP 8000
HP 8200

is to be upgraded.  And rebuilt.  With Windows 7.  For which we have no driver packs!!!  All to be done by Monday - gee thanks!

So my next few posts will more than likely be technical gotchas, quirks and foibles that us deployment engineers encounter...

SCCM OSD Log File Locations

I may be late with this but it's for my reference more than anything.  SCCM OSD can be a hair tearing process at the bet of times.  Should you ever need to troubleshoot it MS don't exactly make it easy finding the files either.

He is where you will find the log files at various points throughout the whole OSD process as they do move dependant on which stage you are up to...

WindowsPE, before HDD format:              x:\windows\temp\smstslog\smsts.log
WindowsPE, after HDD format:                 x:\smstslog\smsts.log
Windows, SCCM agent not installed:       c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Windows, SCCM agent installed:               c:\windows\system32\ccm\logs\Smstslog\smsts.log
Windows x64, SCCM agent installed:       c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
Task Sequence completed:                           c:\windows\system32\ccm\logs\smsts.log
Task Sequence completed x64:                   c:\windows\sysWOW64\ccm\logs\smsts.log

Don't forget - use Trace32 to view these log files - it makes it miles easier....

X1 Carbon Incorrect Hash Errors during OSD

I was fighting with this one for a couple of days.  Lenovo X1 Carbon - deploying Windows 7 x64.  All drivers were fine and dandy but I was getting randon "Incorrect hash value" errors when the OSD was failing.

This was determined by looking in the SMSTS.log once the OSD had failed.

It transpires that if the USB to Ethernet adapter was plugged in to the right hand USB socket it was dropping loads of packets.  Plugging it into the left hand side worked a treat.

As simple a solution as it sounds this may be far too obvious for some tecchy to even try.  I managed to replicate this on 3 different units so it wasn't just faulty parts.

Felt like a complete numpty once I discovered the fix!

Lenovo X1 Carbon PXE Boot Issues

I  was recently given the nice new shiny Lenovo X1 Carbon to play with and deploy our corporate Windows 7 image to it.  To maintain its slim physique it hasn't got a built in Ethernet adaptor and is supplied with a Lenovo USB 2.0 to Ethernet Adapter.  Obviously we now had to track down the driver to inject to our Boot Image.

Initially we used the Lenovo USB 2.0 Ethernet Adapter Driver 5.4.3.0 which PXE booted but then seemed to fail and hang once WinPE loaded up.

I then downloaded the Lenovo X1 Carbon SCCM Driver Pack which came with v5.12.4.0 which also seemed to give me problems.

Eventually I found that it was the manufacturers Vista driver that worked for me.

From the AXIS website you can download the AXIS AX88772B Vista Driver which worked a treat.  With the SSD this was a dream to image and was quite quick in comparison to others.

Hope this helps.

Chris.

Create a bootable USB pen for SCCM Windows 7 Build Deployment

If you are ever in a situation where deploying your OS by SCCM's more conventional methods (ie PXE or LAN based deployments) isn't feasable (bandwidth/no connectivity) then you can prepare a USB pen and deploy to machines via a USB boot.

I've found the SCCM built in method of making a USB pen to be quite unreliable so I opt for the manual method.

Just a few heads up first:

• I'd recommend at least an 8GB drive but in reality your build (if corporate) will eventually exceed this.
• The pen will be totally wiped clean - all data will be lost.

Step 1:  Preparing the USB pen

1. Open command prompt
2. Type diskpart and press enter
3. Type list disk and press enter
4. Find your disk in the list
5. Type select disk * (* being your number)
6. Type clean and press enter - you should see "DiskPart succeeded in cleaning the disk."
7. Type create partition primary and press enter - you should see "DiskPart succeeded in creating the specified partition."
8. Type select partition 1 and press enter - you should see "Partition 1 is now the selected partition." 
9. Type active and press enter - you should see "DiskPart Marked the current partition as active."
10. Type assign and press enter - you should see "DiskPart successfully assigned a drive letter ..."
11. Type detail disk and press enter.  For this example we will work with a drive letter "U" for USB
12. Type exit to leave the Diskpart command and return to a standard prompt

Step 2:  Formatting & Copying

We are still using a drive letter "U:" so we want to type:

format U: /fs:fat32 /q YOU WILL LOSE EVERYTHING ON THE PEN HERE

Enter a label for the drive - this is how it will show in "Computer"

I copy the files manually - it works - but if you want to do it "properly" use this command:

In command prompt navigate to the location of your build files - this is what would have been extracted from the ISO that was produced in SCCM when you "Created Removable Media" from the OSD task sequence - if you need a guide on this mail me or leave a comment...

Type xcopy \*.* /s/e/f \ 

With our extracted ISO in C:\Win7Build and our pen being U:\ This would look like:

Type xcopy c:\Win7Build\*.* /s/e/f U:\ 

Don't forget you may/will need to adjust the boot order in the BIOS to accommodate booting from USB - you can find a guide here: http://bit.ly/TvndIW

Task Sequence Fails Error 0x80040104

More fun and games with OSD Task Sequences - this time in the form of error 0x80040104.

The error as it was displayed on the clients screen was:

This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, please contact your system administrator or helpdesk operator.

This happened immediately after selecting the task sequence and processing the dependencies.

Upon viewing the SMSTS.log we spotted the error

Failed to resolve selected task sequence dependencies. Code(0x80040104)


The only change made to the TS since yesterday was a new driver package for the Lenovo X220T tablets.  The reference to a missing package reminded me of a post I made once in reference to drivers and driver packages - that if you leave the distribution point on Source version 1 it will just bomb out.  Refreshing the DP didn't help so went via "Manage" and created a new source version.


As if by magic..... It worked!

SMSTS.log

Windows 7 Pilot

So the pilot went live today. Our rollout contractor and supplier were both at HQ to watch our first presaged machine go from warehouse to desk and thankfully it built without a hitch.

3 more were put in situ with a further 2 having to go on hold as we had a [unrelated] network outage - apparently it was a touch too warm today for our aircon units in the datacentre.

Really happy with the outcome of Prestaged Media within SCCM and will continue to blog further findings :)

Empty program list in SCCM Task Sequence

I've just come in to find our Windows 7 builds are failing on a specific program that is installed during the task sequence.  It happens it was Trend Anti Virus which I had been working on the previous day.

Before getting into the log files I had a look at the task sequence and noticed that there was no program listed.  Ah ha!  Problem solved > click drop down and select program....  No programs are listed ??!!  I checked the package and I have two programs in there - a standard install and one with verbose logging enabled...

Tried deleting the step in the TS and recreating it... Still nothing...

Resolution

I hold my hand up here - I had changed the interaction to "Only when a user is logged in"

Changed it back and sure enough it was back to normal.


Not so much a problem but it's worth noting - if it's a Friday morning and you haven't had your coffee yet it may catch you out...

Hope this helps someone :)

Error 1723: Can not uninstall JRE update X from Windows 7

I came across this today whilst helping one of our install techs update Java for a customer on a machine he was installing.

It was Windows 7 Ent 64bit SP1 with Java v19 installed.  Upon attempting to uninstall he received the error:

Error 1723: Can not uninstall JRE update from Windows 7.

After a bit of digging around I discovered the error was referring to a missing DLL.

By going into the registry and finding the MSI entry I tried an uninstall using the following command:

msiexec.exe /x{26A24AE4-039D-4CA4-87B4-2F83216019FF}

This was found here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall   -  this is a great tip for any app packagers needing to discover the msi registered to a piece of software for uninstalls etc...

Again I received the same error message.  To enable error logging I added /L javauninst.log and discovered it was missing the "regutils.dll" located here: C:\Program Files (x86)\Java\jre6\bin

I copied the file across from an existing machine and voilà - it worked !

Another Java/MSI quirk but non the less slightly perplexing to say the least. 

Hope this helps someone else sometime...

C

This task sequence cannot be run because a package referenced by the task sequence could not be found.

If like me you have been bashing your head against many firewalls during Windows 7 OSD via SCCM you will probably sometime come across the error:

This task sequence cannot be run because a package referenced by the task sequence could not be found.

More annoyingly it doesn't reference the guilty package in the onscreen error.  After checking the many log files CCM generates I found within the RAM drive path: x:\windows\temp\SMSTSLog resides the relevent SMSTS.LOG file.

The full error I recieved was after selecting the relevant OSD TS; resolving polices and then BAM :

This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, please contact your system administrator or helpdesk operator.

I also noticed (and please use SMS Trace to view error logs):

Failed to find CCM_SoftwareDistribution object for AdvertID="xxx", PackageID="xxx", ProgramID="*"

I found it was a Lenovo Graphics Driver Package causing the issue; it appears SCCM has yet another little "quirk" where the hash isn't written sometimes upon creation of a package and the initial ditribution.  If the version number of the guilty package is "1" try right clicking on the DP of the package and select "Update Distribution Points".

After some time the Source Version will increment to "2" and the date will be current - give your OSD another try and then see if it works - if it fails - check the log file again as this time the guilty package may have changed and it may be a case of trawling through a few before you resolve the issue.

I hope this helps.

Many thanks to J over at ManagedUX for the pointer!