Download Documentation!

System Requirements

• .NET Framework (version 1.1)
• SMS 2003 Advanced Client

Installation and Usage Tips

• Copy SMSView.exe to every system that you want to run SMSView Locally. (See **Note below).
• I install SMSView.exe to my %windir%\system32 directory so that I can go to a run line and type “smsview” and click OK to start the program. ** You can also start SMSView connecting remotely to another system by entering “SMSView Computer1” where “Computer1” is the name of the computer you want to connect to.
• Click the >>>’s to re-run a program.
• SMSView can be resource intensive at times (lots of queries to WMI) – by default, the display updates every 30 seconds. To prevent the refresh, check the “pause refresh” checkbox. Un-checking the “pause refresh” will cause SMSView to start it’s display refresh again on the 30 second interval.
• Enter a computer name into the text box and hit “Query Remote Computer” to query another computer – if you change the computer back to your local computer, it will also work (even though the button reads “Query Remote Computer.”)
• The “History” button will display the last 60 days of Advertisement History (for adverts that have run more than once, only the most recent advert history will be displayed.)

**Note: Full functionality in Windows XP may require permissions modifications on each client you want to mange with SMSView. SMSView_XPPermsFix.ZIP (which can be deployed using SMS) can be used for both modifications (SMS Installer source code is included for SMSView_XPPermsFix.exe). The two issues are as follows:

• Permissions on three WMI namespaces may need to be modified (root\ccm, rootccm\Policy\Machine\ActualConfig, and root\CCM\SoftMgmtAgent) to give the “interactive” and “everyone” specific permissions – these changes can be modified manually or using “WMISetCCMSD.vbs”.
• Permissions to remotely access the registry as identified in MS KB 892192 – this allows a user identified as an administrator on a remote PC to remotely access the registry.

Known Issues and Future Enhancements

• Currently, “Next Run Time” only works for Simple Single-instance Schedule, and for Weekly schedules. I hope to get this enhanced in the next revision. There may be an issue when computing “Next Run Time” if schedules other than Weekly and simple schedules exist for the Advertisement.
• Re-Running an advertisement – when programs have dependencies on other programs (“Run another program first”), this function will not currently work.
• Documentation – I hope to have a little better documentation in the future – For example, sometimes in the “state” field for an advertisement, you may see “WaitingContent” – a good definition of this would be helpful.

Questions? Send me email: ramseyg@hotmail.com