MikeHalliday

So my last deployment had the 500mb partition hidden instead of primary. This forced the dvd drive to be e:. client.msi still fell over due to D: existing but being hidden and not writable! (Out of disk space on D:) Not sure how to proceed now!

Ok, So it looks like I may have solved this. My deployment task sequence partitions the main disc as a 100gb partition and a 500mb partition. It assigns the 100GB partition C: and the 500mb partition as D: It then installs the captured .WIM file to C: drive, which is fine. My client.msi now completes the install, but puts 4 files on D:\Windows\System32\ folder (CCMCore.DLL, CCMPERF.DLL, FRAMEWORKPERF.DLL and ISMIF32.DLL). The D: drive was supposed to be used for BitLocker stuff in the future (And was going to be hidden partition, but I thought I would keep it visible to see what happens - Next step is to build with a hidden partition and see if the client fails again). - This matches up with the client.msi.log I uploaded trying to install to D: drive, via the SystemFolder variable! Is this a bug in Client.MSI? Where it is assuming that OSDPreserveDriveLetter is not set to false and the OS is being deployed to D: ??? - Can anybody try this in a VM and see if it does the same thing? (Reference image created with C: as main disc and D: as cd drive). I would try this in a VM, but our VM infrastructure is only v4.1 and I am waiting for it to be upgraded to 5.1 vSphere (but that could take weeks) (SCCM build and capture using install.wim, C: 100% partition, D: cd drive. Deploy task is a standard SCCM task pointing to the captured .WIM file) - All my pre sp1 customisations have been left out of this new task just to be on the safe side. Thanks Mike.

Hi Guys, I am having big problems deploying W7 onto any hardware since SP1 update! I have rebuilt the Build and Capture sequence and sucessfully made a new .wim file to use i the deployment. Deployment proceeds properly until the Set up Windows and Configmgr task. client.msi.log attached. In the deployment task I have set OSDPreserveDriveLetter to False and the image is installed on E: yet in the client.msi.log file it shows some lines that states; MSI (s) (6C:D0) [11:06:22:073]: PROPERTY CHANGE: Modifying SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933 property. Its current value is 'E:\WINDOWS\system32\'. Its new value: 'D:\WINDOWS\system32'. Then I get [11:06:22] WARNING: Cache directory from WMI: D:\WINDOWS\ccmcache does not exists. Would re-calculate the cache settings. Then MSI (s) (6C:D0) [11:06:22:946]: Product: Configuration Manager Client -- Disk full: Out of disk space -- Volume: 'D:'; required space: 903 KB; available space: 0 KB. Free some disk space and retry. D: drive is the DVD Writer so cant be written to!!! - I assume that if it was pointing to E: all would be good? The package line for Client Upgrade using CCMSetup in the task sequence is as follows; ccmsetup.exe /noservice CCMINSTALLDIR=%Windir%\System32\CCM SMSSITECODE=AUTO I've been trying to find an answer for the failed deployment for the last 3 days, without success. What's wrong, anyone got any ideas??? - The task sequence worked fine before SP1 update. Since the SP1 update I have hit lots of problems (Just like everyone else using it) Cheers MIke. client.msi.zip

Hi, I have searched the whole forum and either my search skills are bad or there is no specific answer to my question?? We are using SCCM 2012 to deploy Windows 7 across the corporate environment and I have hit a small snag. I have 1 task sequence for the whole build process, but we have multiple Windows 7 types that need deploying. My task sequence starts with a HTA that asks what build to deploy 1. Corporate W7 Enterprise (KMS) 2. Corporate W7 Enterprise (Academic MAK) 3. Corporate W7 Enterprise (KMS, restricted Apps) 4. Professional W7 (Individual bare metal OEM license key) 5. Device investigation W7 Enterprise (No apps or customisations - for new hardware device driver finding) Build 1 works flawlessly - KMS activation happens for W7 Ent and Office 2010, all my apps from the task sequence are installed and the build is customised with our branding etc - SWEEEET! Build 2 works, but I cannot see if the MAK key has been activated properly as all the keyfinders show BBBBB-BBBBB etc Build 3 works flawlessly as per build 1 because its checking a TS variable and not installing the un-needed apps! ;-) Build 4 fails spectacularly. Build 5 works great and I can find the missing drivers, create a new driver package and then put Build 1 on to the new hardware. BUILD 4 - This is driving me insane!! After the initial HTA popup (which image to deploy), the W7 pro image selection forces a new popup asking for the OEM key - Once entered it is stored in the %OSDProductKey% TS variable I have 2 unattend files... 1 for corporate build and the other for the W7 Pro build - the only difference is the Pro build has the TS variable in the <Key></Key> section. The Apply OS Image task item points to either unattend.xml or unattend2.xml depending on the results of the HTA selection. My problem is that if I remove the TS variable in the unattend file, I get a full build completed, the Pro 7 is already activated but the key returned by the key finder is completely different to the one I entered via the HTA - The same product key is activated if I run the same process 3 or 4 times!!! - Whos is this product key and where does it come from?? (Is this because I am using an OEM media set as the initial W7 pro image?) - I do have a full Windows 7 Pro iso from MS that I could use if needed? If I leave the TS variable in the unattend file for the Pro 7 build, I get a popup half way through deployment about unable to parse the unattend file and the build fails???? So I guess my question is; How do you taylor a task sequence to install and activate Enterprise W7/Office 2010 via KMS when option 1 is selected or install Pro W7/Office 2010 via MAK or OEM key when option 4 is selected??? There must be a way of doing it - Or am I going about it wrong? - Should I not be asking for the Pro 7 key at all and activating manually by putting in the OEM key once the build has been completed and the machine rebooted? Thanks in advance for any ones help!!! Mike.