Jump to content


Iroqouiz

Established Members
  • Content Count

    342
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by Iroqouiz

  1. Go to Software Library - Operating System - Task Sequences. Left click the OS task sequence and choose the Deployments tab on the menu that appears. Is the TS still deployed to a collection there? Post another screenshot.
  2. I had this exact problem with Dell machines at my old job when deploying Win 7 Ent x64. Started a Technet forum thread where someone suggested using a x64 boot image. I'd been using x86. This solved all my issues. Have seen other random. OSD related Win 7 bugs which were all remediated by using x64 boot image.
  3. Please do share what was wrong and how you solved it.
  4. If you haven't already, integrate MDT 2013 with SCCM. Then create a new task sequence with MDT, this will prompt you to create the toolkit files and settings files packages. Copy this into your CustomSettings.ini file in the MDT Settings Files package directory: [Settings] Priority=DefaultGateway, Default [DefaultGateway] 192.168.20.1=STOCKHOLM 192.168.40.1=SINGAPORE 192.168.60.1=LONDON [STOCKHOLM] SLSHARE=\\STOCKHOLM-SERVER\OSD_Logs\Finished_Logs SLShareDynamicLogging=\\STOCKHOLM-SERVER\OSD_Logs\%hostname% [SINGAPORE] SLSHARE=\\SINGAPORE-SERVER\OSD_Logs\Finished_Logs SLShareDynamicLogging=\\SINGAPORE-SERVER\OSD_Logs\%hostname% [LONDON] SLSHARE=\\LONDON-SERVER\OSD_Logs\Finished_Logs SLShareDynamicLogging=\\LONDON-SERVER\OSD_Logs\%hostname% [Default] Then do your custom tweaks to the TS, whatever it looks like. The SLShare property will copy all the log files after a deployment to the directory you specify. The SLShareDynamicLogging property will copy the log files to that directory specified, in real time, effectively enabling real time logging. Add this as the last step in your TS to actually copy the log files (SLShare):
  5. Yes, you would need to script that. http://www.david-obrien.net/2013/11/redistribute-failed-packages-configmgr-dps/
  6. Double check your driver package (NIC drivers specifically). Check if the machine gets an IP after the "Setup Windows and ConfigMgr" reboot.
  7. 1. Right Click Tools: http://www.nowmicro.com/rct/ 2. Re-evaluation is specified in client settings
  8. The only error I see in the screenshot pertaining to the SUP is "content download failed". Seems like an automatic deployment rule (ADR) has failed to download updates to put in a software update group.
  9. Trust me, use packages, they will never randomly fail. I also used apps before but since a year or so I use packages and haven't had a problem since.
  10. In our environment this happens for (so far) three reasons. 1. The client is not getting an IP address from DHCP (does not apply to you). Solution: make sure the correct NIC drivers are added to the boot image. 2. The date/time is incorrect in BIOS on the client. Solution: set the correct date/time. 3. There are no task sequences deployed to the client. This one is rare but has happened a few times for us. It seems like the client is in some sort of limbo where it's not unknown but it still isn't a part of a collection to which an OSD TS is deployed. And this all depends on how you deploy your TS, do you deploy to "All Unknown Computers" etc. Solution: find out the MAC address of the client and search for it in the SCCM console (create a query from where you can get the MAC address) --> delete the device from the SCCM console. If your OSD TS is deployed to "All Unknown Computers" this is all you have to do. If you deploy to another collection you need to import the device again and add to the correct collection (watch out for limiting collections etc).
  11. Why are you deploying so many updates? How many products do you have ticked? You shouldn't sync, download and deploy updates that are not required by your clients, it just puts your SQL server under unnecessary load, and it will fragment the SQL DB much much faster. If you have many products which makes the ADRs sync many updates each Patch Tuesday you should create a new software update group each time. I would then make one ADR for each product.
  12. The 0x80070643 error code means "fatal error during installation". How are you deploying the client? Client push?
  13. Perhaps an update requiring multiple reboots is deployed and installed? https://support.microsoft.com/kb/2894518
  14. You need to tick "Make this the boot partition"
  15. For me, using a x64 boot image solved the problem. Why I don't know. I created a new x64 MDT boot image and task sequence and tested all newly captured wims on several different models, with different settings, and I couldn't reproduce the problem. Then I tested the old task sequence (basically only difference is that it uses x86 boot image) and the first deployment went fine. The next one gave me the ccmsetup/windings font error again. See this thread: https://social.technet.microsoft.com/Forums/en-US/d2d48f45-01ad-4668-a81f-4e999a205de4/windows-7-becoming-corrupt-after-setup-windows-and-configmgr-step?forum=configmanagerosd
  16. Hey all, Redid my reference images and now I got an issue with several machines I tried doing bare metal OSD on. The TS aborts somehow, it still thinks it's running, after Setup Windows and ConfigMgr. After that step it reboots and I'm greeted with a weird Win 7 logon screen where the font kinda looks like Windings (the font folder on the machine is almost empty, that's why). Looked at the ccmsetup log. This error is listed: http://social.technet.microsoft.com/Forums/en-US/ee4e31cd-d456-44f4-a980-6a785d393d84/ccmsetup-failed-with-error-code-0x80040154-in-ccmsetuplog?forum=configmanagerdeployment The log also complains about BITS, too low version to be able to install ConfigMgr. But obviously Win 7 contains BITS v 4, so I don't get what happens. None of the apps I install in the reference image build I'm able to start (IE 10, Office apps), Office is not even listed in Add/Remove Programs. I have redone the reference images two times, once in plain MDT 2013 and once in SCCM. The error is inconsistent. It happens most frequently on Dell Precision T1700 machines, but not always. Sometimes there's no error when installing the ConfigMgr client and I don't get any font issues, but I still can't start Office apps or IE 10. This is driving me mad. ccmsetup.log and smsts.log files are here if anyone wants to take a look: http://1drv.ms/1ETazJx Please help!
  17. In my opinion Johan Arwidmark's simple but genious MDT tweaks and powershell script is superior to any other reference build solution. http://www.deploymentresearch.com/Research/tabid/62/EntryId/172/Deploying-a-reference-image-VM-fully-unattended.aspx I use this method and it's failsafe. I set up a separate wsus server and approved all my desired updates to the unassigned computers group (does not matter since the build client is the only machine directed to that server). Then you edit the customsettings.ini file with your wsus server. And in the ts you add all the MDT apps you wish. It will take you a day to set this up (craating apps in MDT deployment workbench etc) but you will save sooo much time when its done, and every time you want to build a new image.
  18. In the OCT (office customization tool) you can specify that Office 2013 will automatically uninstall previous versions
  19. Upload the smsts log fike from an affected client.
  20. My best bet is that the client isn't installing the correct drivers. When the client comes back after the reboot, can you hit F8 and ping your SCCM server? Does the client get an IP address? To hit F8 you need to enable command support (cant remember what its called now, on my mobile) in the boot image properties and then update it on the DP.
  21. Appenforce.log or as Niall said the office log file is a better place to look. By the way: I've long since abandoned using apps in OSD. It's just too error prone. I use apps when pushing software to existing clients but during OSD i only use packages. Haven't had a problem since.
  22. Also attach the appenforce log file, if app, or execmgr log file if package. 8004005 is just a generic error like "something went wrong". The real error code is always listed earlier in smsts.log or in this case in appenforce/execmgr.
×
×
  • Create New...