Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. It seems to me that it is a 2012 client trying to assign to a 2007 site and that's not possible.
  2. Did somebody try to push a client to all the systems? The easiest way to make it stop is by emptying the ccrretry.box. This makes the system for stop trying to install the client. So if you still need to push the client you need to figure out why it is generating the access denied messages.
  3. You need to have a package of the ConfigMgr Client, which you also refer to in the Task Sequence.
  4. Once the client is installed and the system can resolve the name of the MP your already good to go.
  5. What's the problem you are running into? Where do you use this script (in the task sequence)?
  6. Why do you want to cut out the branch offices? Do they have their own DP? Also, something that might help, you can use different boundaries for site assignment and content location (and those for content location can overlap). See also: http://technet.microsoft.com/en-us/library/gg712321.aspx
  7. Here is a reference for all the required ports: http://technet.microsoft.com/en-us/library/hh427328.aspx
  8. You have to dig further in your log files then, because these are generic messages.
  9. Important thing is that a network access account is configured, so the client can access the resources. Also this might be handy for pushing clients: http://www.petervanderwoude.nl/post/using-client-push-installation-on-untrusted-forest-systems-with-configmgr-2012/
  10. Couple of questions. Did you check your networkdrivers? Is it domain joined already? Is the client installed?
  11. Where does your task sequence stop/crash? This log files doesn't even come close to installing your applications.
  12. Windows Server 2012 uses a new version of WSUS, so you are not going to get the "Windows Server Update Services 3.0 SP2 setup wizard". Besides that when your are using ConfigMgr for the update deployment you shouldn't configure WSUS via the Wizard, but let ConfigMgr do it for you.
  13. Are you by any change missing the user settings? SCCM installs the application with the SYSTEM account, so that's a difference from you running it from the cmd.
  14. 1. I would start with the WindowsUpdate.log 2. Could also be (actually, even more likely) that your clients are not communicating with the site.
  15. You can set a Maintenance Windows that just occurs one time and gives the system an installation window outside office hours. Just keep in mind that the user won't see anything about the Maintenance Window.
  16. The installation is run as the local SYSTEM account, so make sure that the SYSTEM account has access to the share.
  17. Reporting can help with that, for example report Compliance 2 - Specific software update
  18. 1. Out-of-the-box, you can't change the Package that is configured in the ADR. As I thought that was a bit silly, I figured out how it can be done. Via PowerShell and WMI! Take a look here for more information: http://www.petervanderwoude.nl/post/changing-the-deployment-package-linked-to-an-automatic-deployment-rule-in-configmgr-2012/ 2. Re-create the folder and let the ADR re-run, so it downloads the updates again. 3. The Deployment Packages can be found here: \Software Library\Overview\Software Updates\Deployment Packages
  19. Did you configure IIS and is the Site System computer account member of the local administrators on the DP?
  20. Nope, just a condition for a Task Sequence Variable.
  21. Create both as separate steps and then add on both a condition to check for the existence of the variable.
  22. That's how it's intended to work, because a lot of the information will be configured in (and via) the UDI Wizard (Designer).
  23. This, the Pre-configuration paragraph, is how I did it for configuring Client Push to an untrusted forest: http://www.petervanderwoude.nl/post/using-client-push-installation-on-untrusted-forest-systems-with-configmgr-2012/
  24. Did you check you client.msi.log?
  25. 1. Two Primaries for 200 hundred clients is an "over-kill". 2. The only role that is supported on a cluster is the database. If it's really that important, for that small number of clients, to have a fallback-like-scenario, than you could think about doubling the MPs and SUPs and hosting the database on a cluster.
×
×
  • 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.