SMS 2003 Web Reporting

上一篇 / 下一篇  2006-06-11 15:07:00 / 个人分类:网络技术

SMS 2003 Web Reporting - Remote Tools Page version 2.9
By: Ron Crumbaker
Posted On: 12/15/2004

This is an updated version of the original Remote Tools Web Page. I have added a few more functions, corrected some issues that were pointed out to me.

First you will need to download this file : 10192SMSRemote.zip
It contains the whole folder to setup under IIS. Just unzip the folder and place it on your IIS server and create a new Virtual Directory pointing to that folder.

What I choose to do was create a VIRTUAL FOLDER within IIS on my SMS Reporting Point. Here is a screen shot of my Remote Tools v2.9 Web Page:








As you can see, I have a few custom buttons to find various details about the PC or user.

I created a new Virtual Directory on the SMS 2003 Reporting Point and added the following site \\smsserver\smsremote. Then I put the files found in the download above and setup IIS to that folder.

This has seemed to work great卲lus I can tweak on it without blowing up my SMSReporting point main web page.

***NOTE: You need to set the website link up under IE as a trusted site. And ENABLE all the ActiveX controls for the Trusted sites, even the ones that say Prompt. They must ALL be enabled***


Now for the details of the file:

NOTE - If you already have setup the original version of this tool, all you will need to do is copy everything within the SMSRemote folder within the zip file to your folder where you created your virtual folder and you can skip the next ten steps below. You will need to make the changes to the machrest.asp

1. copy ads.dll to the system32 folder on the web server(Your SMS Server) and register the dll using regsvr32.
2. Create a folder on your SMS Server called SMSRemote (or copy the entire folder from the zip file above onto your SMS Server)
3. copy all of the files included in the download to the folder created in step 2. (if you copied the entire folder in step 2, you can skip this step)
4. copy global.asa from the sms reporting point to the SMSRemote folder.
5. copy mfc70u.dll and mfc70.dll to the i386 folder of sms(\sms\bin\i386).
6. create a share named Remote$ on the i386 folder of sms(\sms\bin\i386) with read permission
7. go the i386 folder of sms and run regsvr32 pollprov.dll and mofcomp pollprov.mof
8. set IIS directory security on the default web site to basic authentication












9. open internet options and set the site to a trusted site and set all activex to enable
10. Under SQL Server Group, Security, Logins, SMS Database, make sure the user has Public and db_datareader access. I chose to created a group called SMS Remote, and put my help desk users in there. Gave them the db_datareader access and public to ONLY the SMS Database. You do not have to create this group, just make sure the users you want to use this page have these rights.












Changes you need to make to the machrest.asp page are as follows:

Line 15, Find this line:
window.open "//<FQDN NAME SMS Server>/<smsremote>/FilterSample.asp?ReportID=1

Change the server name. It must be the FQDN of the server and virtual directory. Example: SMSServer.domain.com and SMSremote for the virtual directory (created in the steps above)

Line 28, Find this line:
strSiteServer = "<SMS Server name>"

Change the Server name. Example: SMSserver

Line 29, Find this line:
strSiteCode = "<Site Code>"

Change the Site Code. Example: SMS

Line 30, find this line:
strStandingAdvertID = "<SMSCollectionID>"

Change the collection ID for the Top Most collection tree you want to list. For Example: "XR10001c" this is the topmost collectionID of the collections tree that you want in the drop down. The easiest way to find this collectionID is to run the following Report -> All collections Report ID 139

I have created a Collection for New Machines, then under that I have the various other items that each have adverts to. See pic:






So I went and ran the All Collections Report to find the CollectionID of New Machines XP

Line 217, find this line:
window.open "/SMSReporting_<YOUR SITE CODE>/Report.asp?ReportID=97&computername="

Verify that ReportingID 97 is Software registered in Add Remove Programs on a specific computer.
The easiest way to find this is to go and run that report and see which ID it corresponds to and insert the ID number. Edit <YOUR SITE CODE> to be your SMS Site code.

Line 224, find this line:
window.open "/SMSReporting_<YOUR SITE CODE>/Report.asp?ReportID=12&variable="

Verify that ReportingID 12 is Computers for a specific user name. The easiest way to find this is to go and run that report and see which ID it corresponds to and insert the ID number. Edit <YOUR SITE CODE> to be your SMS Site code.

Line 228, find this line:
window.open "/<SMSRemote>/Admin.asp"

Change the SMSRemote to the Virtual Server you created above.

Line 237, find this line:
i=WShell.run ("mmc C:\smsadmin\bin\i386\explore.msc -s -sms:ResExplrQuery=" & Chr(34) & "Select ResourceID From SMS_R_SYSTEM Where Name = '" & strName7 & "'" & Chr(34) & " -sms:connection=\\<smsserver>\root\sms\site_<SiteCODE>")

Change the <smsserver> to be your SMS Server name. For example SMSServer. Change the <SiteCode> to your SMS Site Code. Verify that the explore.msc is in the folder C:\smsadmin\bin\i386 or change this line to point to where explore.msc resides on your local system.


Line 285, find this line:
strsiteserver = "<SMSServer>"

Change the Server name. Example: SMSserver


Line 286, find this line:
strSiteCode = "<SMSSiteCode>"

Change the Site Code. Example: SMS


***Note remove all the < and > when making your edits***

You will also need to edit each of the .vbs files so they point to the correct domain.
Find this line in each of the .vbs files:
UserDomain = "<FQDN DOMAIN NAME>"

And change to the FQDN Name. For example: domainname.com Don抰 forget to remove the < and >.


Feel free to contact me at rdcrumbaker@gmail.com with any questions relating to this article.
A list of all my articles can be found here.
Read my blog's


As I stated in my original I want to thank Edan Yona for the wonderful work done creating the original zip file and helping me get the Remote Tools via the web working here. Without Edan's help, this article would never have happened!! And Michael Schultz for his article http://myitforum.techtarget.com/articles/1/view.asp?id=5197, without this, the Push to Client would not have been achieved.

I special thanks to everyone that emailed me bugs in my original version of this Remote Tools Page and for the ones that tested this version.

TAG:

 

评分:0

我来说两句

显示全部

:loveliness: :handshake :victory: :funk: :time: :kiss: :call: :hug: :lol :'( :Q :L ;P :$ :P :o :@ :D :( :)

Open Toolbar