Jump to content


monkeytennis100

Established Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About monkeytennis100

  • Rank
    Newbie
  1. Ok SO..... I think I have narrowed it down to a drivers issue, if i remove the apply device drivers step from the task sequence it does not drop out with the error but carries on as its meant too with the windows set-up box coming up saying Copying files, expanding files etc. If i put that step back in it reverts to throwing the error every time. Why its doing this i have no idea as It worked perfectly last week and nothing have changed at all to anything since then, no new drivers added, none deleted etc. Can anyone see from the log file which driver(s) it might be causing the issue? Thanks
  2. HI all, Im getting task sequence drop out and 80004005 error when trying to build and capture an image of windows 7. The task sequence worked a week ago but have suddenly stopped but nothing has been changed at all. The OS is downloaded, drivers downloaded then the drop-out occurs just as the Actual windows setup screen appears (blue background saying setting up windows", when the task sequence says "Setting up windows and configuration manager" I have attached the log files I could find, path names from win pe are the file names. If anyone could take a look it would be much appreciated Thanks EDIT: After trying again I've found another log (the one just names smsts.log) file with some more errors if anyone can understand them? x-smstslog-smsts.log x-windows-temp-smstslog-smsts.log smsts.log
  3. Thanks for looking, that what i thought as well, and i was even getting software center to open on the machines as well but still nothing showing up in sccm console. It doesnt matter now as i have re imaged the machines. As this is a new install of sccm i was hoping to push the client out to the machines then initilise a reimage from the console but i cant figure out so having to go round to each machine.
  4. Hi, I am trying to do a client push install on some computers but somewhere it is failing but I cant figure out where. Here is a section of the ccm.log form the server.... ======>Begin Processing request: "2097152702", machine name: "HSN998" SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) Execute query exec [sp_IsMPAvailable] N'HSN' SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Attempting to connect to administrative share '\\HSN998\admin$' using account 'heles-school\systemadmin' SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> The 'best-shot' account has now succeeded 42 times and failed 4 times. SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Connected to administrative share on machine HSN998 using account 'heles-school\systemadmin' SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Attempting to make IPC connection to share <\\HSN998\IPC$> SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Searching for SMSClientInstall.* under '\\HSN998\admin$\' SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> System OS version string "5.1.2600" converted to 5.10 SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Service Pack version from machine "HSN998" is 3 SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Mobile client on the target machine has the same version, and 'forced' flag is turned on. SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Creating \ VerifyingCopying exsistance of destination directory \\HSN998\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Copying client files to \\HSN998\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Copying file "D:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Created service "ccmsetup" on machine "HSN998". SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Started service "ccmsetup" on machine "HSN998". SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Deleting SMS Client Install Lock File '\\HSN998\admin$\SMSClientInstall.HSN' SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) Execute query exec [sp_CP_SetLastErrorCode] 2097152702, 0 SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) ---> Completed request "2097152702", machine name "HSN998". SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) Deleted request "2097152702", machine name "HSN998" SMS_CLIENT_CONFIG_MANAGER 07/08/2012 09:46:26 5036 (0x13AC) It says it has started the ccmsetup service on the client but then has a line about an error which i dont understand. I looked at a log file found from google and a sucessfull log didnt have an error line there. The folders are on the client, c:\windows\ccmsetup and i have attached the log file from the client here Thanks for any help you can offer. ccmsetup.log
  5. Thanks, thats what I have found out, If you leave the field blank in the tast sequance, its stays where it is is AD Thanks
  6. In a deploy task sequance you can set the AD location of the machine to build to, can you how ever have the machine detect the location (OU) that is is currently in and build to the same place or do you have to have a different ask sequence for every AD location? Thanks
×
×
  • Create New...