Showing related tags and posts accross the entire site.
-
I noticed that the Configuration Manager SDK link that is shown on www.microsoft.com/smserver is turning up a page not found, it points to http://mscompub/dmt/dialogs/preview/preview.aspx?d=preview&user=deniselr&familyid=064a995f-ef13-4200-81ad-e3af6218edcc&languageid=f49e8428-7071-4979-8a67...
-
A word document (due to so many screenshots) showing how to easily create SQL2000 queries for use in SMS2003 Reporting I get a lot of SQL query creation questions, so thought writing up a short document on how to use SQL2000 Enterprise Manager to build complicated (well reasonably) SQL queries would...
-
Here Alice, this should work this time :>
-
SMSMap has been around for quite a while, if you are not aware of it - why not? it is an awesome tool, have a look at this article Jeff Tondt has released an update - thanks Jeff To download the new version click here
-
Had a problem from one of the sites I support, they said Network Discovery was not working, it was not discovery everything.. So straight way jump in the log files to try and find out why, all looks OK in there… After a few minutes talking to the site about the problem it became clear. Remember there...
-
A VBScript that will obtain the current value of the SDK Site Control File Serial number from a specified SMS site server, for a specified SMS site servers site sode and change it to a value specified on the command line. Use this script only after you understand the underlying concepts of SDK values...
-
Wrote another script, this one will look for a user\group in a specified local group on a machine, remove it, then insert a User or Group. Handy if you want to remove GroupX and replace it with GroupY, or remove a user and replace with a group, works in any combination. If you use this, test test test...
-
A simple script to remove a User or Group from a machines Local Group, and replace it with a domain User or Group. The script can be tweaked so that you can point it at remote machines, but it has been designed to run locally on a machine. Ideally this should be deployed using SMS. As it stands no error...
-
Picture the following: You upgrade an SMS 2.0 Child Site server to SMS2003, this sites Parent Site server is already SMS2003. A few days later you notice on the Parent Site server that there are still SMS 2.0 components present in the Site Status \ Site Component list for the Child site. Two Components...
-
MS have released a post SMS2003 SP3 Client hotfix rollup As the hotfix says, you can only apply this to SP3 SMS2003 AdvCli's Here's the link