2097 Posted July 7, 2014 Posted July 7, 2014 Hi , seem to be having a few problems with this .. Everything seems setup correctly and the machine gets imaged with our pre-made Windows 7 Wim file . ( which is X 64 ) The problem is even though it is specified in the task sequence , the computers administrator password is not set , also the computer is not joined to the domain ( despite the credentials being correct ) I have used the console during deployment to make sure the PC gets an IP address , which it does . Any one experienced this ? , im tempted to try a x86 image to see if it happens with that Thanks 2097
Sam_Brown Posted July 7, 2014 Posted July 7, 2014 Sounds like the account to join the domain doesn't have enough permissions. Have you set the account up correctly?
2097 Posted July 8, 2014 Author Posted July 8, 2014 Account is fine , im using a domain admin account as a test . verify also works . I'm thinking it could be my deployment image , as we have OEM licences , i have installed the certificates and activated in cmd prompt ? ( so is effectively a oem machine )
mrbios Posted July 8, 2014 Posted July 8, 2014 Account is fine , im using a domain admin account as a test . verify also works . I'm thinking it could be my deployment image , as we have OEM licences , i have installed the certificates and activated in cmd prompt ? ( so is effectively a oem machine ) Could be drivers? By default task sequences list the network settings above the driver installation. Rearrange that so that it installs the drivers before the network settings and see if that does the trick, and ensure the network driver for that machine is in the driver package you're using. While you get an IP in the SCCM console after PXE, it tries to use the network driver once the OS is deployed, so could be going wrong there
2097 Posted July 8, 2014 Author Posted July 8, 2014 i have tried drivers applied during the sequence and also added them to the boot image , i have also rearrange the task sequence multiple ways . I find it strange it does not activate the Administrator account also !
Sagima Posted July 8, 2014 Posted July 8, 2014 Just tried it myself. Not going to be any help as I also got the same problem with the local admin account
2097 Posted July 8, 2014 Author Posted July 8, 2014 Just tried it myself. Not going to be any help as I also got the same problem with the local admin account Did yours manage to join to the domain ? i can live without the default Administrator account.
Sagima Posted July 8, 2014 Posted July 8, 2014 Yes it domain joins fine which is probably one reason why I haven't noticed it before as I just logged in as me.
2097 Posted July 9, 2014 Author Posted July 9, 2014 Ok , i just deployed a straight Windows 7 image using SCCM .. and it worked fine . But if i have installed windows 7 on the machine already ( using a CD ) , customized the OS and used the catcher CD to make a WIM and then deploy that image ... none of the rest of the task sequence works such as changing PC name , re-enable the Admin or join domain ) is this normal for 2012 ? , with 2007 and XP i could build a image on a machine and catcher the WIM and deploy with SCCM
mrbios Posted July 9, 2014 Posted July 9, 2014 Ok , i just deployed a straight Windows 7 image using SCCM .. and it worked fine . But if i have installed windows 7 on the machine already ( using a CD ) , customized the OS and used the catcher CD to make a WIM and then deploy that image ... none of the rest of the task sequence works such as changing PC name , re-enable the Admin or join domain ) is this normal for 2012 ? , with 2007 and XP i could build a image on a machine and catcher the WIM and deploy with SCCM I can't speak for certainty, but when i first started using SCCM i was lead to believe that you couldn't import your existing WIM images. I think there is a way to do what you want (not that i've tried, as i just create an installer for everything and have whatever software is required installed via task sequence) but i think it involves imaging a machine with SCCM then modifying it, syspreping it etc. Again though, years since i did that and i haven't looked into it. Be interesting to see what you discover though.
Sagima Posted July 9, 2014 Posted July 9, 2014 (edited) I don't usually use the physical disc for the base install. I import the wim from the dvd iso and set the task sequence to install it to the c drive with uk locale. I then customise that with the software that is on all the computers (office, flash, java etc) and capture it. Then I create a new task sequence based on the build and capture sequence, delete the capture bits and amend the build bits (such as setting it to deploy the 2-2 image from the wim that I just created and setting the local admin password). That task sequence then becomes the admin/office computer task sequence and I copy it and add install software steps for the classroom teacher machines. I have second image, based on that one, done for the ICT suites in the same way with extra bits added onto the copied task sequence for room specific software and to put it on the domain in the correct ou. Saying that, however, I am 99% certain I have done an image from the x86 dvd that I have captured and redeployed without incident using sccm 2012. I am pretty sure I haven't done it with the x64 disc You might want to try just amending the build and capture task sequence and seeing if that works rather than creating one from scratch if you haven't already done so. If you like I can send you screen shots of my build task sequences Edited July 9, 2014 by Sagima
2097 Posted July 9, 2014 Author Posted July 9, 2014 I don't usually use the physical disc for the base install. I import the wim from the dvd iso and set the task sequence to install it to the c drive with uk locale. I then customise that with the software that is on all the computers (office, flash, java etc) and capture it. Then I create a new task sequence based on the build and capture sequence, delete the capture bits and amend the build bits (such as setting it to deploy the 2-2 image from the wim that I just created and setting the local admin password). That task sequence then becomes the admin/office computer task sequence and I copy it and add install software steps for the classroom teacher machines. I have second image, based on that one, done for the ICT suites in the same way with extra bits added onto the copied task sequence for room specific software and to put it on the domain in the correct ou. Saying that, however, I am 99% certain I have done an image from the x86 dvd that I have captured and redeployed without incident using sccm 2012. I am pretty sure I haven't done it with the x64 disc You might want to try just amending the build and capture task sequence and seeing if that works rather than creating one from scratch if you haven't already done so. If you like I can send you screen shots of my build task sequences If you don't mind , could you please post your task seq screenshots
free780 Posted July 9, 2014 Posted July 9, 2014 Does the PC when imaged have a IP address/ network activity ? The boot images in sccm 2012 r2 are win pe 5.1 which is win 8.1 .They have many more nic drivers than win 7. You must add the drivers to sccm and put them in driver packages. Other than that it sounds like the client isn't installing. Try building a VM. Or post the smsts.log .
Sagima Posted July 10, 2014 Posted July 10, 2014 Attached. The task sequences are modified from the build and capture task sequence. I've just shown the ones I've made changes to
free780 Posted July 10, 2014 Posted July 10, 2014 In earlier versions of sccm 2012 I found that if you dont have the fqdn for the domain join user account it can fail to join the pc to the domain. Though it sounds like drivers or lack of a nic driver for windows 7. You can try imaging a pc. Let it fail then use Trinity Rescue Kit | CPR for your computer to enable the administrator account. You can then see if the nic driver has installed.
2097 Posted July 10, 2014 Author Posted July 10, 2014 Thanks all for the help ! , much apreciated . Also thansk for the screens Heres the error from setupact.log Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds Should i be assigning a windows 8 Driver to the Boot image and a Win7 driver as a package to the task sequence ?
Sagima Posted July 10, 2014 Posted July 10, 2014 When you import the drivers to SCCM (by right-clicking on drivers and selecting import drivers) you can add them to a driver package in the wizard. There is already a task sequence step that checks all the packages for compatible drivers - Apply Device Drivers. I add all the drivers for each model of computer I have with that. Usually one model at a time so they each get a separate package but I've never specified a specific package in the task sequence. I haven't ever needed to add network drivers to the boot images in 2012r2 as the default ones seem to work with everything I have but that is done in the driver import wizard as well if you want to. I would only add network or sata drivers to the boot image. Never convinced that the distribute content in the driver wizard works flawlessly so I tend to ignore it and just do it manually when I'm done Windows 8/8.1 drivers for the boot image in 2012r2
free780 Posted July 10, 2014 Posted July 10, 2014 @2097 Just make sure the the domain join account has a fqdn. See Windows 7 – Sysprep Fails to Join Domain, error: 0x52e
2097 Posted July 10, 2014 Author Posted July 10, 2014 you know what i am an idiot ! every time i read that i assumed they meant when joining the domain make sure you use the Fully qualified domain name . I had no idea the user account also needed it ! i have been using DOMAIN\username so i should be using domain.org.uk\username . Im going to give that a go tomorrow and see what happens !
Sagima Posted July 11, 2014 Posted July 11, 2014 I use the short form for domain joining without problems
2097 Posted July 11, 2014 Author Posted July 11, 2014 I think this has now fixed the problem . Just retesting on the correct system .. But fingers crossed ! seems good Thank you every one for the help !
2097 Posted July 12, 2014 Author Posted July 12, 2014 Ok looks like it hasnt solved the problem .. But ! i might have got some where ... Basically i made a image ( using the windows CD ) for our new Fujitsu Q520's ( latest haswell processors etc ) . I acronis'd the image onto a Fujitsu Q510 ( 1Gen older ) . I then captured the image from the Q510 back to SCCM 2012 using the capture CD . I then deployed it back to the Q510 with the task sequence , and it worked fine.. Set the admin account up and joined to domain etc . What i did notice is after i captured the Computer to SCCM 2012 , the machine then automatically went back to windows setup where you could set PC name etc ( which i assume its meant to after capturing ) . On the Q520 it does not do this . So my question to note is ... The capture CD , as this uses the bootimage from SCCM 2012 . Should it have all the necessary drivers preloaded onto it ? ( as im not using a task sequence to capture ). Maybe as these Q520's are really new ..
free780 Posted July 12, 2014 Posted July 12, 2014 It will only have the drivers that are listed in the boot image properties when you made the disk, it will also include any that are built into winpe
2097 Posted July 12, 2014 Author Posted July 12, 2014 indeed , i think i made it quite early on .. So was maybe missing some .. Do i just require Nic drivers in the capture ? or do you think i should add chipset/sata drivers etc as well
free780 Posted July 12, 2014 Posted July 12, 2014 Well you should use hyper v or VMware for the capture. Both of which should have their nic driver in the winpe image by default
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now