Does, anyone have any calculation tools to size a SMS site and rule of thumb to choose either a Primary, secondary, DP, MP, RP etc... site components?
Also based on collected information about IT environment is there any best hierarchy rules.Eg. No# Clients, bandwidth, network rule...
We have our collection is nutted out, back to my question, I should of been abit more clear. Instead of using the SMS MMC console and adding workstations to a "direct" membership, has anyone developed a script or GUI that adds workstation to a collection without using the SMS MMC console. So...
We do have a standard naming convention, does it really matter as long as the script contains the correct machine names? I'm interested how your SQL query works, please advise more...
I am currently trying to work out a nice way for Helpdesk people to add workstations to collections without providing a full SMS training course to educate them. Also provide a script to populate devices into collections. Please note that helpdesk people are generally high turn over, but comes...
Since the hot topic is ensuring the security updates are deployed out to the client successfully, however there are a few occasions that the clients turn the PC of during the night etc... and it is a pain that it installs first thing in the morning or someone has been away on leave for a long...
I ended up recreating the Software Update packages with the appropriate switches (Note: the updates are fussy with parameters). Then the updates was able to exit with the right exit code.
All good now.. thanks.
Now I'm having fun with the Wake on Lan with SMSWakeup from 1e...NOT!.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.