Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. The ConfigMgr 2012 client reacts on the return code of the installation. When the installation returns a code like 3010, it means the installation needs a restart to complete and the client reacts on that. If you don't want that, then you can play with the Should Configuration Manager enforce specific behavior regardless of the application's intended behavior -setting in the User Experience -tab of the Deployment Type.
  2. Build 7782 is the BETA version of SP1 and build 7804 is the final version of SP1.
  3. Running one task sequence from another is NOT possible... There are only lots of 'workarounds' like Rocket Man said. Another interesting one, if you are using Active Directory groups, might be this one: http://www.petervanderwoude.nl/post/new-and-improved-pre-provision-user-applications-during-os-deployment-via-orchestrator-and-configmgr-2012/
  4. It's possible to run them next to each other. Just either watch the boundaries used, or not let it write to the AD.
  5. Take a look at this post: http://blogs.technet.com/b/deploymentguys/archive/2012/10/26/start-screen-customization-with-mdt.aspx
  6. You need to scroll a little bit further to Installed Applications.
  7. The only tool I know is the 1E Migration Tool here: http://www.1e.com/it-efficiency/downloads/1e-tools/
  8. You work from the SCCM console and, unless you did something weird with it, you can just import any WIM image into SCCM.
  9. Ehm... changing from HTTP to HTTPS is a big change... it means you have to start working with certificates. What exactly did you change?
  10. Did you check the log files to see if there is really something going on, or not?
  11. And what the Installation Properties? Also did you check the event viewer for error messages?
  12. Those are already long business hours... are there also any maintenance windows configured on computer (collection) level?
  13. Right click the component and select Reset Counts > All.
  14. Are you using Client Push Installation (like this: http://www.petervanderwoude.nl/post/using-client-push-installation-on-workgroup-systems-with-configmgr-2012/), or are you doing a manual installation? The fact that the ccmsetup.log is filling, means that the installation started. So either way the installation message arrives, but did it start with enough rights and a correct command line?
  15. I don't think it's a SCCM problem. I think you should start looking at the installation log of the applications you're trying to deploy.
  16. You should be able to do that by running a command line like this wusa.exe /kb:xxxxxxx /uninstall /quiet /norestart.
  17. A1: Yeah, you could say that it just has a 24h maintenance window. No maintenance window set, means you can always install your applications/ task sequences. A2: The maintenance windows are iterated and are not specifically for one application and/or task sequence.
  18. Why would you want to try to recover a just installed site after messing with SQL?? Just take the save road and completely reinstall it (that's always the best for your environment).
  19. Looking specifically at System Center, then it can be done with a combination of System Center Service Manager and System Center Orchestrator, like here: http://contoso.se/blog/?p=3085 An other option might be to look at Forefront Identity Manager.
  20. What did you configure in the deployment settings of the task sequence (see Properties of the Deployment and then the tab Deployment Settings)?
  21. During the upgrade to SP1, there is no reason to do something with the existing setup of WDS/PXE...... Did you check the SMSPXE log file to see if this request reached the server, or not?
  22. Take a look at the User Guide, which can be found here: http://h18004.www1.hp.com/products/servers/management/unified/infolibraryicm.html
  23. There should be another SMSTS log file, this one ends with an successful step (Successfully completed the action (Partition Disk 0 - BIOS) with the exit win32 code 0).
  24. When a SUP is configured in SCCM and the Client Setting Enable software updates on clients is set to Yes, then the SCCM client will configure the system, via a local policy, to look at the correct WSUS/SUP server.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.