Harvey

Does it create the folders and the bits tmp files in there or does nothing appear? check the distmgr and despool log. If it's doing something like partially copying the files and appears to be stuck in the process, I've also restarted BITS on the DP on occassions. I try not to restart services on the site server if not all DPs are having issues.

Hello, If I specify the unattend.xml in the "Apply Operating System Image" do I need to sysprep the system using the /unattend switch to the location where SCCM copies it too? It copies it to the c:\windows\panther\unattend\ from teh smstslogs and before capture, that's folder doesn't exist. Thanks!

Do you have to use the MDT boot wim with an MDT task sequence in SCCM or using the built in SCCM would work? I'm wondering why on my SCCM, even though it's 2007, the rules are not being processed only the default section is. I've ran the ztigather.wsf in the command prompt during OSD and see the system information but the rules never process the section I created for it. I'm just wondering if the boot wim matters because I use SCCM boot since I just starting to use MDT integration.

I just use the latest and greatest we have in our company. Whenever they order new stuff I allocate a few for my labs. I talked to our Dell rep and she said there's a new model the 7010 coming out in June so this is already 2 product cycles old now. If you're still using the 620s you'll see a big benefit and even more if you get the Intel SSDs or wait for their new models and get that. I don't benchmark or anything but they run fine for what I need it for. These have Core 2 Duo processors. Not sure if there's a difference between that and I5 or I7.

Kind of late to post but here's my new labs running Hyper-V for SCCM 2012/MDT 2012. Dell Optiplex 780 16GB RAM Intel 520 SSD 240GB - Primary for OS and VMs WD 500GB Enterprise - storage

We just wipe and load, our user's documents are redirected to a share so back up process should be very minimal like IE favorities and such, but htat will change as we migrate to Windows 7 and take advantage of the new redirection policies. I support about 7000 systems in a few states but our company has more and each region has their own IT mgmt and methods. This works for me because I find that computer association would be too cumbersome for the techs to use and they always complain about time consuming processes and wouldn't be able to troubleshoot it. It would be another thing for them to come me with questions about. I'm the only SCCM admin and the techs aren't really able to pick up even the concept of how a Task sequence is advertised to a computer so we just stick to a manual process for backing up data. All reimaged systems have new records created. The same name system w/ the old records will be purged by SCCM in a few days, if the system is reimaged with boot media it will prompt for PC name. Systems that reimaged using RAP will not prompt.

Why not create a command line step with the uninstall string with the old version and in the conditions have it run only if that version is installed? In my experience if i run anything in TS, I have it as a seperate program with no dependencies.

I don't know much about Powershell but If you want to script, you can create one that queries the DB directly instead of using a WMI query. The table is dbo.CollectionMembers. You can search it by name or Machine ID but ID would give more exact if you recently imaged same named systems where the old entry still exists.

I believe you have to sysprep before you capture. At least that how I do it since sms 2003 days. There's a step you can add during the Task Sequence to use a different sysprep file but I never played around with that. I still build the images the old way and imagex to capture then import it.

Dell has a new driver pack, "WINPE 5.0". Check it out, it contains all the drivers for it for WINPE. http://support.us.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R303896&formatcnt=0&libid=0&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=457752 When I added the XP drivers for the TS it froze on me when I used Apply Driver package. When I set it to Auto Apply Driver package it worked fine, not sure why that is case.

You can edit the msi directly and search for the AutoUpdate field and change it to 0 and save it.

Yes, you coudl have just created it. Here's the link to it, it looks like the TSConfig can also be used to save environment variables later on. http://technet.microsoft.com/en-us/library/bb694075.aspx It's good you got it working another way.

Someone at my company found this solution but it was because the new PCs had Dell partitions on it that we used it and not because of Pointsec encryption though it wipes that out too. If you mount your boot image using imagex, there's a file called TSconfig.ini, the other files are the ones you will create and add to it but also needs to be in teh same directory as the TSconfig.ini. What I find annoying about this is that if hte Task Sequence fails to find a TS then the hard drive is already wiped clean. You shouldn't need to format the drive from this script, the TS shoudl have a step to format before you apply the image. Here's the contents of each file, underline is the filename and bold is the contents. This executes automatically when the Task Sequence Wizard loads. You'll see dos windows appear and disappear from teh script running. I have incorporated this script as a package and it worked, this was put in at the first step before naming the system and formatting and apply the WIM. You could try this and see if it works with your current TS w/o creating a new boot wim. If anything you would only need the 2 new files and not the TSconfig.ini if you want to make a package. I havent really tested it out with many systems but it worked on all that I tried. If it odesn't work for you then put it on the boot media instead, that definitely works. TSconfig.ini [CustomHook] Commandline="x:\PreTS.vbs" PreTS.vbs Option Explicit On Error Resume Next Dim oShell, oFso Set oShell = CreateObject("WScript.Shell") Set oFso = CreateObject("Scripting.FileSystemObject") oShell.Run "diskpart.exe /s x:\diskpart.ini",,true Diskpart.ini select disk=0 clean create partition primary select partition=1 assign letter=C active

Hi, I have the MDT 2010 integrated and there's an option to create a boot image. Is there any difference between this and the SCCM default one? Thanks, Harvey

Hello, Has anyone successfully created a boot media or standalone image using a USB 3.0 flash drive? I have a 16GB Kingston USB 2.0 that is detected and works but the AData 16GB USB 3.0 isn't detected during the TS media creation wizard. I have tried formatting it in Vista even though I shouldn't need to for it to be detected. It is detected in Windows and works like a normal drive. Is there something else I'm missing or is SCCM the reason? Thanks, Harvey

See if hte link below helps, is the time set correctly in the BIOS too? http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/9b72f604-04ae-4eec-9e42-405742f10a90/

For our Office 2007 package, the MSP file is in the same directory as the setup.exe. Our command line is just setup.exe which I assume by default references the MSP file there, the xml is not configured and when it was configured would interfere with it. The only problem I have with Office 2007 upgrade from 2003 is that the reporting never fully updates when it's finished installing, setting it to reboot itself or not.

I think the problem is with Windows 2008. I got WDS working on a windows 2003 box and it loads it up faster in a matter of 5-10 seconds. I wonder if it's the network profile that's available in WDS in 2008 that 2003 doesn't have. I set it to gigabit in 2008 because it and desktop are all on the same gigabit switch with gigabit ethernet but didn't think that'd be the issue. I'll change to 100MBs and see if that makes a difference. It's bad enough that imaging is about 1hr 15-25 minutes, don't need another 5 minutes to add to it.

Hello, I got PXE boot working but it's taking over 3-5 minutes to load the boot wim file that's 150MB. My PXE server is on the same gigabit switch as the desktops and is running Windows 2008. At the time it takes to deploy the boot wim file I could have already been half way into deploying the 3.5GB O/S image if I booted up using a CD. It seems to vary on different computers and funny that hte older GX620 are faster in loading the boot WIM faster than the 760 and 745. Since I never had experience with it before it, what is the normal time it takes to PXE boot a wim file? Also if I load more than one boot wim like one for production and one as a test for new drivers, does it prompt an option to load or I should only have one on there? Thanks, Harvey

After talking to our MS rep, they suggested to include this line in the sysprep file. This may or may not prompt the driver install during the image process if it can't find the driver. None of this was showing in the SMSTSlog so it's hard to pinpoint, this may help others with drivers that don't install. In the [unattended] section of sysprep they suggested we add "UpdateInstalledDrivers=Yes" goes before the DriversSigningPolicy. This has worked as a solution to get the drivers to install and join it to the domain and I've just tested it during Driver Injection so it will work with the need to include the drivers on your WIM. My boss encountered a different scenario so he included it on the WIM however it seems to be a hit or a miss when you rebuild your driver packages to make it more neat. I don't know the problem but my ended up looking for drivers in a Drivers/11 folder when it didn't copy them down. Only 1,2,3 existed and in the 3 directory was where the Intel driver were copied to but it didn't find the PROUNSTL.EXE file only. Make sure your unsigned drivers is checked off in the Auto Apply Drivers package too. The driver we used was the one from Dell, hopes this helps.

When you create a boot image, do you use the appropriate drivers for your SCCM version? Ours is upgraded to SP2 and upgrades PE to ver.3. I read you should use Win 7 drivers. I think we used XP drivers which worked for all models except the 755 after some patches to fix some certificate issues. I've tried Vista and Win 7 and it doesn't matter. I see Task Sequence screenshots out there where Apply Network Settings before the Apply Drivers. Does that mean it uses the drivers on the boot image to add it to the domain and continues to the Apply Drivers section? I'm just trying to figure out what driver it's using when it reaches that point, it doesn't seem to matter except on 1 system.

I've tried suggestions from other threads w/ the same network card but it doesn't seem to work with this model when I try to apply it to our Task Sequence. The image pulls down fine and the driver injects fine for other models of Optiplex and Latitude but not the 755. These are the same drivers we had working in SMS 2003 and just imported them into SCCM thinking everything would work except for that one model. If we log into the box and can go into Device Manager quickly enough, we can see that the drivers are there because it will install it but that's after the fact and it's missing half the applications on the Task Sequence and not joined to the domain. I've tried many drivers from Intel, HP, and other variations and versions but none seem to take. Would there be a difference if I selected install all compatible drivers vs select the best driver?

Sorry for bringing up an old thread, when I try this script in my Task Sequence it didn't work. I tested it on my Dell desktop prior and it was able to pull the serial. When I updated the DPs with this and tried it the pop up window didn't contain the serial tag. Did you place your script before or after the partition task or it doesn't really matter? Edit: I figured out the problem, I've made my script pre-fill the serial number in the inputbox and used the wrong variable. All good now. Here's my modified script of the OP and others I found which will prefill an input box with the service tag. In my environment, we add the state, site code, and dash before the service tag. This will save you from having to flip the laptop and reading the small stickers or bend down in someone's nasty cubicle to read it. Our environement is 100% Dell so I can only confirm it works on Dell systems. Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & "." & "\root\cimv2") Set colSMBIOS = objWMIService.ExecQuery("Select * from Win32_SystemEnclosure") For Each objSMBIOS in colSMBIOS strserial = objSMBIOS.SerialNumber Next default=strSerial sNewPCName = InputBox ("Please enter a computer name to continue." & Chr(13) & Chr(13) & "Serial Tag: " & strSerial, "Computer Name", default, 30,30) env("OSDComputerName") = SNewPCName env("ComputerName") = SNewPCName env("HostName") = SNewPCName

Gotcha, you mean when you select the TS that's advertised menu. Is there any way to speed up the sync'ing? I thought these changes would be instant since I am booting off the CD every time I make a change on the actual server not from my desk console. This is a production server already but we haven't migrated anyone to it so it's not really get much use yet until we get the MDT operating 100%

Hello, First, I want to note that we have 100% working OSD - Task Sequence. With that said, I've duplicated that one and added an extra command line for the Computer Naming Script and disabled programs to install. After updating the DPs and running the CD again, the TS failed to run at the Computer Naming section. When I came in the next morning and ran it again for the hell of it after trying to figure out why it didn't work. The logs weren't helpful. Anyway, the script was working. Now that my script was working I've enabled programs that I disabled earlier and now my TS would fail at the programs that I've enabled. I disabled Office earlier and now enabled and it fails there. My question is are TS changes on the fly or is there a wait time for it? I was under the assumption it was on the fly but it doesn't seem like it or could it just be a coincidence? Thanks, Harvey