Free Training! SMS Scripting Excercises from MMS 2005

Microsoft provides quite a bit of free SMS training online such as SMS Scripting: MMS Lab Exercises. While attending MMS is not free, these exercises are!

VBScripts can help you with just about any SMS related tasks. The MMS 2005 Lab exercises were designed to teach some common solutions to the daily chores for SMS Administrators.

After running through the lab, you will be able to connect to the SMS Provider, access objects, and perform simply tasks with fewer button clicks. This of course will free up your hand for a nice cold Red Stripe.

Here are a few of the tasks the lab covers:
  • Create an SMS package and program
  • Read an SMS package and program object
  • Modify an SMS package
  • Delete an SMS package
  • Create an SMS advertisement
  • Modify an SMS advertisement
  • View available SMS queries
  • Run a specific SMS query
  • Summarize an SMS site's health
  • View an SMS collection
  • View and Modify the SMS Advanced Client cache
  • Check the status of the Advanced Client agent
  • Use Windows Management Instrumentation (WMI) CIM Studio to view and modify object data
Your SMS 2003 site should be running on a Windows 2003 server, and be configured as an SMS 2003 primary site server. A Windows XP (pro) computer with the SMS Advanced Client installed and pointing to the site.

Don't have an SMS 2003 lab? What are you waiting for? Get a free copy of Virtual PC, and set one up using evaluation copies of Windows Server, and SMS 2003!

Don't forget to check Amazon.com for some great SMS 2003 books, such as the SMS 2003 Administrator's Reference: Systems Management Server 2003.

Comments

Post a Comment

Popular posts from this blog

SMS "Program failed (run time exceeded)" 10070

When a program fails due to error 10070, it does so because the Run Time was Exceeded. SMS Allows a program to run for 12 hours, afterwhich it will issue the failed status message if the program hasn't completed successfully. Note: The Maximum allowed run time within program properties is generally a guide for users running the program themselves, and is not enforced.
Read more

SMS "Waiting for User Condition" 10036

Status Message ID 10036, or "Waiting for User Condition" can occasionally grind advertisements to a halt. Make sure the environment and user condition settings for a particular program have been configured appropriately and are not excluding a large portion of your intended audience. Related Articles SMS WQL for All Clients where Last Status is Waiting for User Condition SMS Status Message ID's
Read more

SMS "Waiting for content" 10035

Status Message ID 10035, or "Waiting for content" is a common error which can drive you up the wall when testing a package deployment. Have you checked your site boundaries? Often a client is located in a IP Subnet which hasn't been configured within Site or Roaming Boundaries. Has the software been deployed to the clients local DPs? Check the reports and console, make sure the package has been deployed and is available to the clients. Is the advertisement configured for download and execute? Check the DP, make sure BITS is enabled, and the web site is functioning properly. Have you checked the logs? Start with the cas.log and execmgr.log on the client computer. Related Articles Clients do not send a status message when an advertised program is disabled in Systems Management Server 2003 SMS Status Message ID's
Read more