Jump to content


anyweb

Root Admin
  • Posts

    9244
  • Joined

  • Last visited

  • Days Won

    368

Everything posted by anyweb

  1. well if you look at your component logs what are they complaining about ?
  2. i'd follow my RTM guides here http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/ start with part 1, this guide was written when the Release Candidate was out...
  3. start by reading this http://blogs.technet.com/b/oob/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx
  4. correct, so adjust the user's rights appropriately so that they can add more pcs such as below Override the Default Limit of the Number of Computers an Authenticated User Can Join to a Domain You can override the default limit, using the following method: (via > http://support.microsoft.com/kb/251335) Expand the Domain NC node. This node contains an object that begins with "DC=" and reflects the correct domain name. Right-click this object, and then click Properties. In the Select which properties to view box, click Both. In the Select a property to view box, click ms-DS-MachineAccountQuota. In the Edit Attribute box, type a number. This number represents the number of workstations that you want users to be able to maintain concurrently. Click Set, and then click OK.
  5. so why not share what you found out so others can learn :-)
  6. check your custom client settings that's what is most likely 'installing' the SCEP client, if you followed my guide, if you didn't follow it totally then you may have edited the default client settings which would apply to ALL computers in your hierarchy
  7. well have you tested the script running in system context using psexec ? how are you doing the restart ? as the built in step or some other way ?
  8. what does your smsts.log file say ?
  9. exit code 1 usually means that it can't find the file, so are you specifying the file correctly ?
  10. I'm still in the process of writing the RTM guides which have got as far as part 9... they take a LOT of my time to do and prepare, and I do it all in my own time, once I feel I have the time/patience I'll reproduce them in word format or similar. cheers niall
  11. on the client you are deploying have you verified if it has an ip address ? is it a virtual machine ? if so what type (vmware/hyperv ?)
  12. then you need to configure Role Based Administration as I describe here.
  13. the one thing that would worry me immediately is the number of concurrent connections to a Windows 7 client versus to a Windows Server
  14. it's best practise to target the ADRs and antimalware policies and custom client settings to specific collections that are created to target the correct machines, if you target the All Systems collection with these ADRs, custom client settings and custom antimalware policies then you are targeting everything and then you'll realise that making custom antimalware polcies (for servers for instance) just won't work in your scenario.
  15. note that this is taken further in System Center 2012 Configuration Manager Service Pack 1 - see here for details.
  16. 1000 users would tell you not to use a CAS, one primary with some dp's underneath should be good enough ! you can throttle with dp's now
  17. this part of the guide is specifically about Endpoint Protection, can you please raise your question as a new topic elsewhere ? also f.y.i installing configuration Manager 2012 on Server 2012 is NOT supported until Service Pack 1 is released (early 2013 timeframe)
  18. SP1 beta to SP1 final will not be a supported route, SP1 beta is for lab use only (not production) http://www.niallbrady.com/2012/06/20/how-can-i-upgrade-system-center-2012-configuration-manager/
  19. yes upgrade from RTM to SP1 final will be supported, you'll do it from a top down method in your hierarchy, so cas first, then primaries then secondaries and your clients..
  20. that was a guess, the guidance is early 2013 so anytime in the first quarter i assume
  21. also make sure you've spelled System Management container correctly, the Component Status Logs will reveal your issue,. right click on one that shows up as red, choose show all, then read the logs for the failure messages see below as before, double check every part of my guide as you've made a mistake somewhere...
  22. well what error are you getting now ? are you running this via PXE boot or within Windows ?
  23. hi all, the video of my session at the Enfo Workplace day in Malmo Sweden is now online, please have a look, share and tell me what you think of it :-) and here's my PowerPoint from the event (PowerPoint 2013) download it here > Deploying Windows 8 with System Center 2012 Configuration Manager Service Pack 1.pptx cheers niall
×
×
  • 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.