Jump to content


GauiC

Established Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About GauiC

  • Rank
    Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. No one had this problem with 64bit boot image? I should also mention that my 32bit boot image has 802.1x support and that setup is also on my 64bit image.
  2. Hi, I have been using SCCM to deploy Win7 32bit to computers but just started to work on 64 bit OSD. The problem that I have is that my 64 bit boot image continuously reboots, I don't even get to the point where I choose my task sequence. What I have done is: created new 64 bit boot image, enabled F8 command line support and injected network drivers. also enabled F8 support on the default 64bit boot image. Created bootable usb with both of the boot images (for testing). However, when I use the boot images it will boot into Winpe but then it will just reboot again into the same winpe... and loop over and over until I just shutdown the computer. The strange thing is that F8 support does not work, that is when I press F8 to troubleshoot the problem in Winpe, nothing happends. I have tried to remove F8 support, build the boot image again and reenable F8 support (and build again), but no go. My 32bit boot image works fine. Any ideas on what could be happening? GauiC *edit: forgot to mention. My setup is SCCM 2007 SP2 R3
  3. Hi, I am currently deploying machines over 802.1x network and am using user authentication to achieve this, however I found one problem. The computer being deployed does not retrieve machine certificate until sometime after the OSD has finished. I have created a vbscript that creates an inf file (putting the hostname into the inf file). Then I use certreq to create the request, submit and accept cert from the enterprise CA. This is all done in my win7 deployment task sequence while in current OS (not Winpe). I have tested this on a computer that has been deployed and it works fine. However during the OSD I get this error: Error title: Certificate Request Processor "The requested resource is in use. 0x800700aa (WIN32/HTTP: 170) machine.inf([NewRequest] Subject ( "CN=testcomputer.mydomain.com")" If I skip this step I am always needed to run a fix after each OSD where I change the authentication mode from user to Machine (802.1x). Any idea on what could be wrong? How are others doing this? GauiC
  4. Hi, I am having a problem during the build and capture Win7 phase. My build phase is currently set up as this: 1. I import computer information (use only MAC address and name), for a virtual machine. 2. Add the imported computer account in a build Windows 7 collection. 3. Deploy all software updates (that are being deployed in my company) to Build Windows 7 collection (and also All Unknown Computers). 4. My build and capture task sequence deploys win7 using installation media (not image), I am using Win7 with SP1 integrated media. The Setup windows and configmgr step is installing hotfix kb2509007, and pointing to SMSSLP and SMSMP. 5. Then I have 3 Install Software Updates steps in a row all using "All Software Updates". (here the problem starts) The first Software Updates step deploys 45 updates, then the step initiates a reboot and the next steps run however now they report that no updates are needed for the machine. That would be great if it where true however the computer is missing some updates. The task sequence then finished as expected, creating a new wim file but missing at least 12 updates. When I logon to the newly build machine and run Windows Updates, it connects to my SCCM server and tells me that no updates are available, but when I check for updates on windows update site then I am given these 12 updates. I am guessing that during the first software update phase, SCCM notices that the computer is a member of Build Windows 7 collection and deploys updates according to that, but after the reboot initiated then it does not locate the machine (that is why I also tried to deploy all the updates to All Unknown Computers). However I am not able to get this working. I have checked that the updates missing are downloaded and deployed in the Software Update branch in SCCM. The updates that are missing are some .net4 updates along with IE9 and Updates for Windows 7. I am not deploying any software in my build and capture phase, just pure Win7 images. Any idea? Is this similar to how you are building your images? GauiC
  5. If you don't use protected distribution points then Singapore clients can be connecting to France distribution point or UAE distribution point. You set up protected distribution points to make sure that clients that are in a specific boundary, only connect to that distribution point. For information on how client chooses a distribution point: Configuration Manager and Content Location (Package Source Files)
  6. Is the Singapore distribution point set as protected for the Singapore boundaries? About Protected Distribution Points How to Configure a Protected Distribution Point
  7. Update: ok, I have tested deploying Windows 7 SP 1 image and added updates to that image during build and capture task sequence, and it works flawlessly. So it seems like that this is a problem related to building an non-SP1 image and updating it with post-sp1 patches. You would think that patches that require SP1 should not install at all but I guess that I have only two options now: 1. hurry the project of testing sp1 in our corporation and then deploy new machines with sp1. 2. try build and capture again but add fewer patches at each time to find out the patch that is causing this.
  8. I just tried now to change the task sequence to use Operating System Install package instead of an image (as a starting point for my new image). the software update task ran as normal, now with 83 updates installing, it rebooted after installing the 83 updates an the next step was to run the software updates again (as it is needed to run few times to get all updates in). But it fails just like before, after reboot the computer does not continue running the task sequence and gives me the login promth. smsts shows me the same information as before, that the task sequence environment is not found. I will try to add SP1 to the image and see if that will fix the problem.
  9. I created an image about six months ago using the same Task Sequence, so this is a new problem. Not sure that it matters, but Windows 7 SP1 has not yet been deployed in our company as it is still going through some tests. Could it be possible that some newly released patches require SP1 and therefore makes software updates installation get this way?
  10. I am almost certain that the System Update task is causing this, the last two advertisement status for this task sequence are: The task sequence execution engine successfully completed the action (Install Software Updates) in the group (Build the Reference Machine) with exit code 0 Action output: r job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... Waiting for job status notification ... NotifyComplete received Received job completion notification from Updates Deployment Agent Reboot Required Setting TSEnv variable SMSTSRebootRequested=HD Setting TSEnv variable SMSTSRetryRequested=TRUE Installation is not yet complete, action needs to be re-run after reboot Setting TSEnv variable SMSTSInstallUpdateJobGUID=. then followed by this status message: The task sequence execution engine performed a system reboot initiated by the action (Install Software Updates) in the group (Build the Reference Machine). No more statuses appear after this status, and the computer that was used for the reference displays the logon promth. I am using test task sequence and test image while I am finding out the problem (I don't want the "uh oh" ) I also tried to disable the Software Updates Task and then the task sequence runs smoothly and finishes correctly. Looking through the log files I notice one out of the ordinary: the smsts.log file included these lines: The action (Install Software Updates) requested a retry Reboot to local harddisk _OSDGinalsConfigured variable set to TRUE _SMSTSServiceStart Type variable set to Calling RebootSystem() OSD type of task sequence. ignore the service window setting ... then after reboot a new smsts.log is formed and this is listed there: Failed to set log directory. Some execution history may be lost. The system cannot find the file specified. (Error: 80070002; Source: Windows) Executing task sequence !sVolumeID.empty(). HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,467) !sTSMDataPath.empty(). HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,1395) Task Sequence environment not found. Task sequence completed in Windows PE. Uninstalling Setup Hook ...
  11. Hi, I have been updating my images somewhat regularly, however I've stumbled onto a problem that I haven't figured out how to solve. My setup is, SCCM 2007 SP2 R3. Deploying Windows 7 Enterprise and Professional 32 and 64 bit images. (Not yet deploying SP1 for Win7) My task sequence is quite simple (wizard generated mostly): Build the Reference Machine Restart in Windows PE Partition Disk 0 default settings, except enabled Quick format. Apply Operating System changed this to deploy the latest image instead of deploying from source files. (the image here is the latest image I used in deployments) Apply Windows Settings I am not entering product key here, but have enabled the administrator account and set the password (for troubleshooting) Apply Network Settings joining workgroup only Apply Device Drivers auto applying only network adapters (saving time) Setup windows and ConfigMgr using parameters: SMSSLP=<MySCCMServer> SMSMP=<MySCCMServer> SMSCACHESIZE=15360 PATCH="C:\_SMSTaskSequence\OSD\<SiteCode>00011\i386\hotfix\KB2509007\sccm2007ac-sp2-kb2509007-x86-enu.msp" Install Software Updates All Software Updates Capture the Reference Machine Prepare ConfigMgr Client Prepare OS Capture the Reference Machine I advertise this to all unknown computers along with all the updates that I am deploying. When running this task sequence now, it runs smoothly until it finishes the Install Software Updates task. After the update task finish the computer is restarted by the install software update task and the following line is displayed in the advertisement status message for the build and capture advertisement: The task sequence execution engine performed a system reboot initiated by the action(Install Software Updates) in the group (Build the Reference Machine). However the reference computer now starts to initialize the configMgr client but reboots and shows me the logon screen, and nothing more is reported in the advertisement status message for the build and capture advertisement. If I logon to the reference computer I notice that the folder _SMSTaskSequence is available on the C: drive and also the ProvisioningMode is set to true in registry. I am thinking that maybe some update is causing this problem but I am not sure what would be the best way to troubleshoot this. Any ideas? GauiC
  12. Hi, I am having the same problem, exit code 1619 when installing fingerprint software on 64bit OS. Did you find a solution to this problem? GauiC
  13. Hi, I have this scenario: Some client computers need to be relocated to new users. Some of the computers are using bitlocker and the recovery key is stored with the computer account in AD. For some of the computers the data needs to be stored so the hard drive is removed from that computer and stored in a secure place. Then a new hard drive is purchased and used in that computer, the computer account is reset in AD (by resetting the account and not delete, the bitlocker recovery history is stored in the AD account). The computer account is deleted from SCCM. The machine is then reimaged using OSD that is advertised to unknown computers. Software distribution is controlled by AD groups, so when the computer account is reset the helpdesk employee that resets the account will also remove all software deployment groups from that computer object and then put that computer object in the new software distribution groups. Now for the problem. When the OSD has finished installing Windows 7 onto the computer the SCCM console displays two records for that computer account, one that is Heartbeat discovered. That record is marked with a client, assigned and not obsolete. Then the other record, that is AD System and AD System Group Discovered, it is not marked as obsolete (obsolete = <null>) and it has all the ad groups that should then be used in the software deployment phase. The solution that I use now is to delete the record that is AD System and AD System Group Discovered and then during the next discovery schedule for AD System Group Discovery the correct record will be updated. I would really like to get rid of that extra step, that is to delete the duplicate record manually. Any ideas? GauiC -Update Created this in the wrong SubForum, this should have been under Troubleshooting, Tools, Hints and tips.
  14. Update on this issue. The reinstallation of the distribution point was maybe part of the solution but not enough. To fix this issue I had to monitor BITS on the branch distribution point using bitsadmin /monitor /allusers and if there was an error I would use: bitsadmin /info <jobid> /verbose > logfile.txt Then I would review the logfile.txt and see what's causing the error, in my case there was a file extension (.resource) that had to be allowed in the applicationhost.config file (%windir%\system32\inetsvr\config\applicationhost.config) If there are more than one jobs running I would use bitsadmin /suspend <jobid> and then bitsadmin /resume <jobid> to force that job to retry. So now the issue is solved.
  15. Hi, I am currently deploying Windows 7 and enabling Bitlocker is one of the last step of my task sequence, so one of my issues is that after the OSD the computer will be encrypting for a few hours. I have heard that it would be better to enable bitlocker before applying the OS itself, has anyone done that and if so what would be the procedure for that? (and should that shorten the time it takes to enable bitlocker on each machine?) GauiC
×
×
  • Create New...