Grab our RSS feeds Follow us on Twitter Join our Facebook Group Connect with us on LinkedIn
myITforum.com, Powered by You.
you are not logged in

Articles

Newslinks

Links

Downloads

Site Services

Community Forums

Discussion Lists

Article Search

Newsletter

Web Blogs

FAQs

Live Support

myITforum TV

Take a Poll

Monthly Drawing

myITforum Network

User Group Directory

Our Partners

About Us

Register

Login

BRONZE PARTNER:

BRONZE PARTNER:



Industry News:




  Home : Articles : Web Technologies print | email | | Forums |   print | email | | Blogs |   print | email | | Wiki |   print | email | | FAQs |   print | email | Article Search  
SMS 2003 Web Reporting - Remote Tools Page version 3.21


Bookmark and Share

By: Ron Crumbaker
Posted On: 1/5/2006

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.


Here are a list of changes that I made in this version:
New layout
New Refresh Policies button
Push to Client has Refresh Policies tied in to it
Remote Assistance has grabs the PC Name
Filter Button reworked
More Documentation
Repair Client
Reworked the Admin Script Page
SMS and SQL on different servers corrected


First you will need to download this file : 10775New Web Remote v321.zip

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 v3.21 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…plus I can tweak on it without blowing up my SMSReporting point main web page.

If you already have the version 2.9 working, then you can skip to the Editing Section.


***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. Plus you need to add the SMSReporting Point as a Trusted site as well.***


Now for the details of the file:
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
3. copy all of the files included in the download to the folder created in step 2.
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 created a group called SMS Remote, and put my helpdesk users in there. Gave them the db_datareader access and public to ONLY the SMS Database.
11. Copy the images folder to the Virtual Directory folder















Editing Section

-------Admin.asp Page---------
Edit line 22 - This will need to be the FQDN of the Domain.
'You will need to edit the following line to fit your environment.
UserDomain = "Domain.Domain.com"

-------Default4.asp Page-------
Edit line 12
<!--'You will need to edit the following line to fit your environment. SMSSiteCode is your SiteCode of your SMS Server Name.-->
<p align="center"><img border="0" src="../SMSReporting_SMSSITECODE/Images/SMS_Gradient.gif" width="547" height="64"></p>

Edit line 19
<!--'You will need to edit the following line to fit your environment. SMSSiteCode is your SiteCode of your SMS Server Name.-->
<p align="center"><img border="1" src="../SMSReporting_SMSSITECODE/Images/bnrSMS.gif" width="200" height="48"></p>


-------Default.asp Page-------
No Changes required

-------Filtersample.asp Page-------
Edit Line 42 - You will need to edit the Data Source which is your SQL Server Name and the Initial Catalog which is the SMS Database name.
'You will need to edit the following line to fit your environment. Data Source and Initial Catalog
strConn = "Provider=SQLOLEDB;Data Source=servername;Initial Catalog=sql-databasename;Integrated Security=SSPI"

-----MachRest.Asp Page-------
Edit Line 16
'You will need to edit the following line to fit your environment. SMSServerFQDN is your FQDN of your SMS Server Name. SMSServer.DomainName.Domain.com
window.open "//SMSServerFQDN/smsremote/FilterSample.asp?ReportID=1", “filter","resizable=yes,scrollbars=yes,width=300,height=350,top=100,left=100"

Edit Line 31
'You will need to edit the following line to fit your environment. SMSServer = Your SMS Server. Leave the ""
strSiteServer = "SMSServer"

Edit Line 33
'You will need to edit the following line to fit your environment. SMSSite Code = Your 3 Digit Site Code. Leave the ""
strSiteCode = "SMSSiteCode"

Edit Line 35
'You will need to edit the following line to fit your environment.
strStandingAdvertID = "SMS0001B" 'For Example: "XR10001c" this is the topmost collectionID of the collections tree that you want in the drop down

Edit Line 147
'You will need to edit the following line to fit your environment. SMSServer = Your SMS Server Name
Set objPing = GetObject("winmgmts://SMSServer/root/default:PingPoller")

Edit Line 149
'You will need to edit the following line to fit your environment. SMSServer = Your SMS Server Name
path = "\\SMSServer\remote$\remote.exe"

Edit Line 155
'You will need to edit the following line to fit your environment. SMSServer = Your SMS Server Name oWshShell.run path & " 2 " & addresses(ubound(addresses)) & " \\SMSServer\",0,false

Edit Line 167
'You will need to edit the following line to fit your environment. = Your 3 digit Site Code. Remove the <>. parent.frames.output.location.href "/SMSReporting_/Report.asp?ReportID=1&variable=" & CompName

Edit Line 203
'You will need to edit the following line to fit your environment. = Your 3 digit Site Code. Remove the <>. parent.frames.output.location.href "/SMSReporting_/Report.asp?ReportID=97&computername=" & CompName & "&SortRs1Col=1&SortRs1Dir=1"

Edit Line 213
'You will need to edit the following line to fit your environment. = Your 3 digit Site Code. Remove the <>. parent.frames.output.location.href "/SMSReporting_/Report.asp?ReportID=12&variable=" & CompUser

Edit Line 219
'You will need to edit the following line to fit your environment. SMSRemote is the Virtual Directory for this tool. parent.frames.output.location.href "/smsremote/Admin.asp"

Edit Line 229
'Currently this function requires the SMS Admin Console to be installed on the local system 'You will need to edit the following line to fit your environment. SMSServer = Your SMS Server. = Your 3 digit Site code. Remove the <>.
i=WShell.run ("mmc C:\smsadmin\bin\i386\explore.msc -s -sms:ResExplrQuery=" & Chr(34) & "Select ResourceID From SMS_R_SYSTEM Where Name = '" & CompName & "'" & Chr(34) & " -sms:connection=\\SMSServer\root\sms\site_")

Edit Line 279
'You will need to edit the following line to fit your environment. SMS Server = Your SMS Server Name
strsiteserver = "SMS Server"

Edit Line 281
'You will need to edit the following line to fit your environment. Sitecode = your 3 digit site code for SMS
strSiteCode = "SITECODE"

Edit Line 374
'The following lines will need to be edited for your location - Edit SMSServer to be your sms server name
Set objPing = GetObject("winmgmts://smsserver/root/default:PingPoller")

Edit Line 400
'You will need to edit the following line to fit your environment. This is your SQL Server Name
ServerName = SQL Server

Edit Line 402
'You will need to edit the following line to fit your environment. This will be the SMS Database Name.
DataBase = SQL_DatabaseNameforSMS

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://www.myitforum.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.

I am working on the next version of this tool, so if you would like to see a feature included in the next version, please email me and I will try to get it included.

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.
My blog

  myITforum.com ©2010 | Legal | Privacy