Jump to content


CorradoGuy

Established Members
  • Content Count

    43
  • Joined

  • Last visited

Community Reputation

0 Neutral

About CorradoGuy

  • Rank
    Advanced Member
  1. The problem is on the SCCM server and it is not updating its cache so I will pass this onto the SCCM Admin. As per a recommendation from one of the users on the Microsoft site I checked the cache and it is still holding onto the old files.
  2. Thank you for the reply but I am not trying to re-run the same deployment, this is being run on a new machine each time. Better said I am deleting my test machine from SCCM and re-imaging it and I get this. It will pull down the image without an issue but it pulls down the old version of Office and not my updated package.
  3. We recently changed from a District to a City so I have changed the MST file in my Office 2010 application to reflect this but I am still getting the old name. I run the installer manually and it comes up with the correct name so I deleted the content from the DP and then pushed the new one and now I can deploy ijust Office 2010 with the new name in the application. As a final test I pulled down an image through my Task Sequence and when it installed Office 2010 it had the old install files. There were a number of older MST files in the original install folder so I removed these and left the current one in the root folder and the updates folder in the source. After I pulled down an image I checked the cache and sure enough it was using the old install files and not the ones I modified. Does anyone know if a Task Sequence caches installers and if so how do I get rid of them? I have searched and couldn't really find anything that mentioned this. I have... - Updated the SCCM application with the newer source files and delted the old ones from my DP and uploaded the correct ones - I have removed the step in the task that installed Office 2010 and added it again but it still uses the old files - I have confirmed I can push out just Office 2010 byitself and it will use the updated source files Using SCCM 2012R2 and currently testing the deployment on Windows 7 Pro x64. Thanks for any input.
  4. When does it fail? Will it even try applying the image or does it apply the image, reboot, and then fail? Have you enabled the 'F8' option on your boot menu and then check to make sure your network can get an IP address, I do a 'ip config' to see if I have a proper network connection. It sounds like there is something in your task sequence that SCCM can't find. This can because you don't have a network connection or a step in your task sequence is looking for a file that no longer exists.
  5. I don't use this method so I can't help you with your original problem but I did add how I capture images to the end of this post which may help you out in a non-automated method.... http://www.windows-noob.com/forums/index.php?/topic/4800-capturing-a-reference-computer/
  6. Why not just use Imagex? I use a VM for all image creations because I add other apps and found this was the easiest way. I created a WinPE CD with imagex installed and then I boot my reference machine from the WinPE boot and then change the CD drive and enter the following..... imagex /capture C: C:\Win7.wim "Windows 7 Enterprise" imagex /capture (tells imagex to capture an image) C: (I only create a single partition with my Windows 7 install so it is easy to capture, this steps tells it to capture only the C: drive) C:\Win7.wim (This tells imagex to capture the C: drive as a .wim image and name it Win7.wim) "Windows 7 Enterprise" (This is the label you will give the image, make it anything you want) Once I capture my image it will be stored on the root of the C: drive on the reference machine so I only need to copy it to the location where it is stored. You can also use 'net use' to map a drive in DOS and copy it straight to the server share but this is the fail safe method as I had some failures during the capture. I know this doesn't help with the original question but this is how I work around this issue with a machine that has never been added to the domain.
  7. I am working on our side-by-side migrations to take users from one machine to a new replacement machine, in this round the users all have Windows XP machines and the new machines are Windows 7 machines. We are using SCCM 2007 R3 on a Windows 2008 R2 server if this makes a difference. - When I first tried this upgrade I ran into the KB974571 issue on the XP machine which inserted the null characters into the SCCM certificate which caused the restore to fail on the new Windows 7 machine. - To correct this I removed the KB974571 update and then ran 'ccmcertfix.exe' which is part of KB977203 update and ran it again and it worked. For this upgrade I used the MDT replacement Task Sequence and just removed the disk wipe part and it seems to be working properly. - I start this upgrade by doing a simple USMT scan on the Windows XP machine after the association has been created in SCCM. Once the scanstate part has been run on the XP machine and the users data is stored on the SMP I run the next task sequence. The next task sequence formats the drive and then installs a clean copy of Windows 7 and then restores the users data back to the Windows 7 machine as expected. So that works but it is not very efficient, I have to run the scan on the users machine first and then once this is done I have to manually start the next task sequence on the new machine to install Windows and then restore the users data. This means there is a day turnaround at least where the users data is being changed but the state store is not being updated. I have been searching and it is stated that you can't use the 'scan' task sequence to start the 'image & restore' task sequnce which is really too bad. It would be nice to be able to capture the user state from one machine and use that task sequence to image the new machine and restore the users data to the new one overnight when nobody is around. Because it doesn't seem like we can chain one task sequence to another one when capturing the user state and then restoring it to a new machine all in one go I tried another method. I imaged a clean machine with Windows 7 and then created the association and then I ran the scanstate on the XP machine. Once this was done I ran the state restore on the clean Windows 7 machine I made earlier but the restore fails out each time with the same error that points to the KB974571 issue. As a test I took the Windows 7 machine and I ran my first task sequence which installs Windows 7 cleanly and then restores the state store and this worked. So I know the data I scanned is fine and when the OS is intsalled at the same time the restore works but if I try to run the restore by itself on a clean machine it fails. In all of my tests I did touch the association between the two machines so nothing has changed here. If I install Windows and do the restore in the same task sequence it works but if I try to restore to a built machine it fails. 1) Can you actually apply the user state to a machine that already has a clean image on it? 2) Did I get poor information when I was researching, can you do a scan of one machine and then use that task sequence to start the imaging of the new machine so I can do this all in one step? Thanks for any help, Dennis
  8. I think the HAL is the same on both machines, they are showing up as multi-processor HALs so it must be something else. I think it is the SATA/AHCI drivers that are causing the issues, how do you address the SATA/AHCI drivers when you sysprep the image? On my really old machines I have to add the SATA/AHCI drivers manually and add some extra lines to the sysprep file before I do the actual sysprep. With the newer machines I do this through SCCM but in these machines there is a AHCI mode in the BIOS but the earlier machines don't have this so I do it through sysprep. The last post in this thread shows how I got rid of the blue-screens and the same error you got... http://www.windows-n...n-all-machines/ Sorry, after reading through your post again you are working with new machines so you will need to force the SATA/AHCI driver through SCCM. I wish I had a good link that would describe what I mean but within your Task Sequence you will need create a driver package with your SATA/AHCI drivers and then use a WMI Query to check for your target machine. In your driver package you would match the driver and model and push this to your machine. The first paragraph would deal with the early machines and this one would do the newer machines.
  9. Yes you can, this thread goes over just that.... http://www.windows-noob.com/forums/index.php?/topic/1735-using-offline-mode-in-windows-pe-using-usmt-4-via-a-task-sequence-in-sccm-2007-sp2/
  10. Just to bring this thread to a close I did get all of our machines to image off of one Windows XP image. The first step was to ensure all machines used the same HAL which ours did, they are all ACPI Multiprocessor machines so there was no messing around with the HALs on these machines. You can check this by opening the Device Manager and under 'Computer' you can see what HAL is installed. The second step was to find the AHCI drivers for each machine and add an extra line in the sysprep.inf that pointed to the specific driver for the machine. To do this I got the AHCI drivers from Intel but you could use the OEM ones as well. I created the following entries in the sysprep.inf and then added the drivers in the C:\Drivers folder. [sysprepMassStorage] PCI\VEN_8086&DEV_2825=C:\Drivers\Lenovo\M55\ATA\ich78ide.inf PCI\VEN_8086&DEV_27C0=C:\Drivers\Lenovo\M52\ATA\ich7ide.inf PCI\VEN_8086&DEV_24DB=C:\Drivers\Lenovo\S50\ATA\ich5ide.inf PCI\VEN_8086&DEV_2651=C:\Drivers\Lenovo\S51\ATA\ich6ide.inf The last step I made was to add the following entry to have the machine go through and build the driver list.... [sysprep] BuildMassStorageSection=Yes In the end that was all it took, for the machines that SCCM couldn't inject the AHCI drivers I simply remotely connected to an existing machine and found the PCI\VEN number and then supplied its driver. I created a program in C# to do all of the finishing steps with the machine and delete the temp files and the drivers folder then assign the machine to the user and delete/modify the user accounts on the machine. I also do all of the steps recommended in this thread as well as a number of other steps to clean the base image up which I found on in a number of threads I found on the internet. This thread is really good, there are about 7 parts and it is really good to read through this for machine prep.... http://remyservices.wordpress.com/2007/09/28/sysprep-in-depth-part-1-adding-drivers-to-our-image-pc/ Note: I do not set the local administrator password, if I set this in Sysprep SCCM fails to apply the Windows XP image. Instead I leave the password blank and have SCCM set it through my Task Sequence which works properly. ------------------------------------------------------------------------------------------------------------------------------------------------ ;SetupMgrTag [unattended] OemSkipEula=Yes InstallFilesPath=C:\sysprep\i386 UpdateServerProfileDirectory=1 NonDriverSigningPolicy=Ignore TargetPath=C:\WINDOWS KeepPageFile=0 [sysprep] BuildMassStorageSection=Yes [GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=4 OemSkipWelcome=1 [userData] ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx FullName="xxxxxxxxxx" OrgName="xxxxxxxxxx" ComputerName=PCCLONE [TapiLocation] CountryCode=107 [setupMgr] DistFolder=C:\sysprep\i386 DistShare=windist [identification] JoinDomain=DomainName DomainAdmin=DomainName\User DomainAdminPassword=Password [Networking] InstallDefaultComponents=Yes [sysprepMassStorage] PCI\VEN_8086&DEV_2825=C:\Drivers\Lenovo\M55\ATA\ich78ide.inf PCI\VEN_8086&DEV_27C0=C:\Drivers\Lenovo\M52\ATA\ich7ide.inf PCI\VEN_8086&DEV_24DB=C:\Drivers\Lenovo\S50\ATA\ich5ide.inf PCI\VEN_8086&DEV_2651=C:\Drivers\Lenovo\S51\ATA\ich6ide.inf
  11. After your TS has run Diskpart are you running a 'Format and Partition Disk' to create the new partition for Windows to be applied to? I set the first command in my TS to restart in Win PE and the next step is to partition the hard disk and then apply Windows to the partition.
  12. I would think adding a command line to the start of your Task Sequence would do the trick. Try a test, open your Task Sequence and then click the 'Add' button and select 'General' and then 'Run Command Line.' Under the Command Line in the new entry try the following and see if it works (without the quotes)... "cmd.exe /c diskpart /s diskpart.txt" If the diskpart.txt is not local then you will need to fully qualify the path for this file. Have you tried the partioning tools within the Task Sequence to see if you can get them to do this for you? I use it to create a 1.5 gig partition for the boot files, DaRT, and Bit Locker (if needed in the future) and it works well for me. BTW, why are you using Diskpart? It will not remove any encrypted data so if you run file recovery software it will find a lot of what was on the drive. I work with high security stuff as well but we run Department of Defence Wipe which takes 7 passes of the drive and will remove everything.
  13. When you go to update your collections also make sure to right-click the package and select 'Manage Distribution Point' and then select 'Update all distribution points with a new package source version' to ensure all files are updated and or replaced.
  14. In SCCM you would right-click the Task Sequence and use the 'Create Task Sequence Media' option and then create your boot media. This media would allow you to boot into SCCM for any Task Sequences you had made. If you use a MDT boot image it will look to MDT for a Task Sequence. Basically they are not the same, one will boot into SCCM and the other will boot into MDT as far as I am aware.
  15. I'm not really sure on this one, I do a build but I have to do a manual capture as not all of my needed software will install through SCCM. I also customize the default profile so I need to logon to the local admin profile so it is never captured through SCCM. Once I finish my customizations I always use imagex to capture the default image and then manually upload this to the server so I never have this naming issue.
×
×
  • Create New...