Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

Everything posted by kcdinga

  1. Hello, We are finally getting around to setting up pxe boot for sccm 2007 r2. The sccm server is installed on a Server2003 SP2 box, so WDS is already installed. The DHCP Server is separate from the SCCM server and on a same subnet. I have done the following: 1. enable the PXE Service Point role on server 2. Checked the following boxes under the PXE Service Point Properties: Allow this PXE Service Point to Respond to Incoming PXE Requests, Enable unknown computer support, Require a Password <set the password>, Respond to PXE requests on all network interfaces. I did not change the Delay (seconds)...I left that at 0. 3. Also on the PXE Service Point Properties tab, I left the Use Computer Account to connect to the database. and left the Certificate as the default. 4. On our DHCP Server, we set Option 66 using the IP of the SCCM Server 5. On our DHCP Server, we set Option 67 using the path of the reminst folder containting the pxeboot.com file (we used the IP address of the server in the path) I have read Peter Van Der Woude's blog Peter's Blog And I have downloaded the PDF "Mastering PXE Boots" by Dominik Heinz. The picture below shows you what happens when we boot: There isnt an error message, so I am grasping at straws. Any help is greatly appreciated. Thanks, Ray Theiling
  2. Ahh...thanks Peter, I will make that change then. Does anyone see a problem patching my previous wim file? rather than creating a new from source files? We have a couple of special configs that I couldnt accomplish with the unattend.xml file, so this way, I do not have to use the unattend.xml with each patch update for the image. Thanks, Ray
  3. When I patch, I only patch the Security Updates. It actaully has been a discussion around her for a bit. I believe Mandatory files are the patches that I have downloaded and deployed (correct me if I am wrong). Thanks for the post...it helps to know I am on the right track.
  4. Hello everyone, A couple months ago, we had Neil Peterson from Microsoft into the office to help us with a couple of SCCM 2007 R2 items. One thing we talked about is patching the Windows 7 Image every couple of months, to cut down on build time. I am currently working on a task sequence that will accomplish this task. I am using Windows Virtual PC, and have set up a new VSD that will boot to my Capture.iso The task sequence will do the following: Build Reference Machine 1. Restart in Windows PE 2. Partition Disk 3. Apply the Windows 7 WIM that we are currently using 4. Apply Windows Settings 5. Apply Network Settings - Joining to a Workgroup 6. Apply Device Drivers 7. Set up Windows and ConfigMgr - During this step, we use the FSP="SCCM SERVER NAME" and SMSSLP="SCCM SERVER NAME" 8. Install Software Updates - Have it set to Mandatory Software Updates Capture The Reference Machine 1. Prepare ConfigMgr Client 2. Prepare OS 3. Capture the Reference Machine - Caputres WIM to network location I would like to get some input on what everyone else is doing? Or if anyone sees issues with this task. I can start this task at night, before going home, and it finishes by the time I get to the office in the morning. I then just have to copy to my Distro Points. So how is everyone else accomplishing this task? Thanks, Ray
  5. I ended up canning the whole usage of USMT 4.0 in SCCM for side by side migrations. Now I use a batch file that includes the command line for USMT Scanstate and Loadstate using offline migration. I basically do the following: 1. build my new machine using SCCM 2. Pull the hard drive from the old machine and connect it to the new machine (either via USB or E-Sata) 3. Plug in a USB thumbdrive containing USMT 4.0 and my batch files for both scanstate and loadstate 4. Verify the drive letters match the drive letters in my command line in the batch file (there are many ways to get around this step...I am just lazy) 5. Run Scanstate.bat (this runs scanstate using the following command line: e:\USMT\x86\scanstate.exe C:\Migrate /offlineWinDir:F:\Windows /o /localonly /c /efs:copyraw /v:5 /l:E:\Logs\scanstate.log /progress:E:\Logs\scanstateprogress.log /i:E:\USMT\x86\miguser.xml /i:E:\USMT\x86\migapp.xml /uel:90 /ui:ats\* You will want to modify this, as I am only pulling domain profiles...so ATS is our domain You will notice that I am saving logs back to the thumb drive...I am scanning a windows folder on the E drive (the drive we pulled from the old pc) and a local store on the new pc C:\migrate. 6. Run Loadstate.bat (runs the loadstate on the new pc) e:\USMT\x86\loadstate.exe C:\Migrate /c /v:5 /l:E:\Logs\loadstate.log /progress:e:\Logs\loadstateprogress.log /i:E:\USMT\x86\miguser.xml /i:E:\USMT\x86\migapp.xml /lac /uel:90 /ui:ATS\* Again, we are running the loadstate from our thumb drive...it is saving the logs to the thumbdrive...and it is restoring the data from the mig file created on the local C drive from our scanstate. It just works for us...seems pretty simple, and cuts down on the amount of time to migrate data. We migrated 17GB with 15000 files..took 12 minutes to scan...and 9 min to load. Hope this helps. PS- the batch files are simply the code snippets above...just copy and create a batch file with each of the command lines (and adjust for drive letter differences and whatnot)
  6. Thank you for your response Niall...This is one area that I just am not getting for some reason. Would the steps below seem logical? or do you have a better way to accomplish this? 1. Create a task to Capture user settings in SCCM. 2. Create a collection for the capture of the source computer user settings 3. Advertise the task to the newly created collection from step 2 and make it available to boot media 4. Create a task sequence to build the machine and restore user settings in sccm 5. Create a collection for the restore/build of bare metal equipment 6. Advertise the task sequence to the Restore collection from step 5 and make it available to boot media 7. Import computer information from the bare metal machine in to computer association, and associate the Source and Destination computers 8. Add Source computer to the collection from Step 2 and boot using the boot media 9. Add Destination computer to collection from step 5 and boot using the boot media I really appreciate the help! This site is really great for us users who are not as experienced. Ray ps- I really do not know the reason why I cannot use PXE boot on our network. I was just told as I moved into this role, and managing our older BDD setup that we could not. We have some new blood on our Network Engineering team, and I think its time to bring this up again. I will let you know what their reasoning was for "do not pxe boot"
  7. Hello, I am working on some task sequences to migrate data during a side by side migration in OSD. We are using SCCM 2007 R2 with MDT 2010 integrated. I have USMT 4.0 installed on the primary site. I have used ANYWEBs recommendations, and can get the In Place Migration with Hardlinking to work just fine, but I need a solution when upgrading the hardware also. Up until now, I was under the impression that I could create a Computer Association (Source and Destination) and then use a single task sequence to capture the data from one pc, migrate it to a Storage Point, apply the image to a new baremetal machine, and then restore the data to the new machine. I have imported the Side by Side Migration task sequence from ANYWEB, and it does show a single task sequence that will accomplish this...however, I believe you need to pixie boot, and we are unable to pixie boot due to network configuration issues. Is there a way, to use two separate task sequences to capture data and restore data to a new machine? I would assume I could create a collection for the source computer and the destination computer...import my baremetal pc and associtate it with the source computer and then advertise the tasks (one to the collections. Would I be able to use boot media for the bare metal machine? I appreciate any help you can provide. Ray
  8. USMT 4.0....piece of cake!

  9. OK Peter, so after reading your reply...I started looking a little closer...and I am an Idiot :-) I was making changes to the SCANSTATE and not the LOADSTATE... Sooo....I adjusted the Restore User Files and Settings task to use the "Customize how user profiles are restored" selection...chose no configuration file...and voilla...I was able to migrate only the domain users. Thanks for pointing me in the right direction..hehe... Ray
  10. Yes, it is very clear...we can't use the /ALL with /UI...that makes sense. The problem is I am using SCCM 2007 SP2 with USMT 4.0...so I am not actually creating the command line (the one that is using /all...) I have a task called Set Hard-Link Load Parameters....that sets the task sequence variable: OSDMigrateAdditionalRestoreOptions....the value of this variable is /Hardlink /nocompress /ui:premconf.com\* I also have a task called Capture User Files and Settings...where you will choose the User State Migration Tool Package...In this task, there is a setting for Capture All User Profiles with Standard Options...or you can choose Customize how user profiles are captured...and gives a button to choose the files...I assume this is where the /all is coming from in the command line...I have chosen the second option on this, the customize how user profiles are captured...but I do not know how/where you would enter files. So my question is this...how does a normal person use SCCM 2007 SP2 with USMT 4.0 to migrate only Domain Users? I appreciate any help you can provide. Ray
  11. Hi Peter, For out situation, we do not want to migrate any local accounts...only domain accounts. When I use the /ui: ats\* I get an error...stating the /all cannot be used with /ui...I am trying something different right now...where I went into the task sequence and chose the second option...rather than Migrate All Profiles. The second option allows you to use a custom file...but I do not know what that file would be...nor where to store it... It did allow me to not choose a config file when applying the changes to the task sequence in SCCM...We will see what happens. Have you had anyone else have these issues in the past? The whole process doesnt really seem like rocket science, but its kicking my butt. Thanks for your help, Ray
  12. I am getting frustrated. I have been working on getting USMT 4.0 using hardlinking working in SCCM 2007 SP2 for a few days now. At one point, I successfully migrated a domain user. Somewhere along the line, something has changed. I am now getting the following error on loadstate: I am using the demo Task Sequence from this site to Migrate Windows XP users to Windows 7 using Hardlinking. I have added /ui:premconf.com\* to the Set Hardlink Load Parameters variable. The command line looks like this: I have read the scanstate and loadstate syntax info on technet...And I noticed in the Task Sequence in OSD, I have to either choose Capture all user profiles with standard options or Customize how user profiles are captured and provide configuration files...so I assume this is where the /all is coming from. Any help on this would be greatly appreciated. I was excited yesterday to overcome some hurdles, only to go right back to having issues today. Thanks KCDINGA
  13. So even though I have a specific OU selected in the network settings, it will override if it sees an object in a different OU? Thanks for your help
  14. I apologize if this has been talked about, but I have searched around quite a bit and have not found the answer I am looking for. Is there a way to have the machine join the domain using an existing object in AD? Here is the network portion of the task sequence I am using: 1. Migrating from Windows XP to Windows 7 using SCCM 2007 sp2 OSD 2. Starting the process from an advertised task sequence on the machine to be refreshed 3. Apply Network Settings - Join a Domain: premconf.com Domain OU: LDAP://OU=New Builds,OU=Premiere Computers,DC=premconf,DC=com Account: domain account we use to join machine to domain. I assume this is happening because I am specifying the OU...I did see a post on this site that talked about using a variable for the Domain OU, but was unsure if that would fix this issue. Any help is greatly appreciated. KCDINGA
  15. OK...that worked. (when I say that worked...I meant, only migrating the domain profiles) but thank you for your reply! soooo...and I will post this next question in another thread... How can I get the object to join back to the domain using the existing object :-)....but like I said, that is not a question for this thread. Thanks, KCDinga
  16. After doing some more searching...I found another forum (which had a post from anyweb in it...) with the /ui:domain\* tag...to just copy domain level profiles. I added this to the task sequence and am testing now. I wasn't sure, so I added the tag to both the Set Hard-link Scan Parameters and teh Set Hard-link Load Parameters...we will see how that works. I will post back with the results. kcdinga
  17. Hello, I am working on setting up the migration from Windows XP to Windows 7 using SCCM SP2. I used the demo task sequence provided on this website (which was fantastic), however, I am running into an issue. I will provide logs from the failed migration after I explain a few things about the build. 1. We change the name of the local administrator account from administrator to trogdor (yes...the burninator) via group policy. I think what is happening is the scanstate is scanning the trogdor account successfully, however, when the machine is disjoined from the network, the account reverts back to its original name of administrator. When the loadstate tries to load, it fails becuase it cannot find an instance of trogdor. In the loadstate log, its states this: I also noticed my build did not rejoin to the network, but that is understandable, as I did not delete the original object in AD...so it was not able to create a new object in the OU I have chosen in the task sequence. Any help is greatly apprciated. The scanstate, loadstate and smsts logs are attached to this post. Kcdinga loadstate.log scanstate.log smsts.log
  • Create New...