-
-
Roger Zander has released v2 of his famous Client Center tool, if you don't know what it is, I highly recommend it, you can get it from here.
Here is a tweak which will let you run PSExec from the custom command tool instead of just a standard command prompt.
Download PSExec from Windows Sysinternals copy PSExec.exe to install location (default is) “C:\Program Files\SCCM Tools\SCCM Client Center”
Edit SMSCliCtrV2.exe.config
Change the following values:
From
To
-
-
Recently stumbled across these add-ons for your favourite browsers, Firefox, IE6 only... makes browsing a lot more fun and easier.
Cooliris | Discover More
CoolPreviews by Cooliris, Inc.
Click-less browsing
CoolPreviews (formerly Cooliris Previews) is a free browser add-on that lets you preview links and rich media without clicking or leaving your current page, so you can browse the web faster than ever. Simply mouseover your link or our CoolPreviews icon, and a preview window instantly appears with your content. No more clicking back and forth!
Interactive preview
Fully interactive on just about any website, including Google, Yahoo!, MSN, YouTube, Flickr. Also try CoolPreviews on blogs, discussion forums, news sites, and and more. Discover More, Faster
- Fly through search results, web links, and more without clicking.
- Avoid the hassle of clicking in and out of unwanted links.
- Customize CoolPreviews to work on a per site basis.
- Free of adware or spyware.
Choose your flavor
CoolPreviews works on Firefox and on Internet Explorer 6.0 (support for v.7.0 and 8.0 not available). Our Firefox version has many more features and is continually updated. Click here to see our
comparison chart.
-
-
Here is an add-on to Ron's Web Remote Tools page, to check the last time a Collection was updated, this works for both SMS & SCCM. This will pop up an hta and present the Collection ID, Collection Name & Time Last Updated of all your collections.
Edit machrest.asp (take a back up, always better to be on the safe side) add the following around line 80ish or at the end of your other buttons, <input style='WIDTH: 180px' type='button' value='Date of SMS Collections' name='Btn735' ID='Button735'>
Add the following sub near the bottom, before </script>
' Collection last updated?
Sub Btn735_OnClick
compname = trim(document.frmMain.txtValue.value)
Set WShell = CreateObject("WScript.Shell")
set fso = CreateObject("Scripting.FileSystemObject")
strSMSServerName = "ServerName"
strDMSourceFldr = "\\" & strSMSServerName & "\Remote$\"
strcmdending = "\\ServerName\Remote$\lastcollection.hta" & chr(34) & " -c: -h: -m:" & chr(34) & compname & chr(34) & " -a:1"
wShell.run chr(34) & strDMLocalFldr & strcmdEnding,1,vbFalse
End Sub
' gtk ends Collection last updated?
Copy lastcollection.hta to your Remote$ share.
Edit lastcollection.hta lines 62-64 with your values.
<p><h3 align = left><font color='Orange'>The Server name is: SERVERNAME, and the Site code is: XXX</font></h3><div></div>
Site Server Name: <Input Type = "Text" Name = "SqlServer" value="SERVERNAME">
Site Code: <Input Type = "Text" Name = "Database" value="XXX">
Credit goes to MeenEnta (aka George K) for sharing the add-ons, see forum post here.
-
-
Here is an add-on to Ron's Web Remote Tools page to check the a PC’s ConfigMgr Client Health state using Greg Ramsey’s ConfigMgr Client Trouble-shooter, more details about this available here
Edit machrest.asp (take a back up, always better to be on the safe side) add the following around line 80ish or at the end of your other buttons, <input style='WIDTH: 180px' type='button' value='ConfigMgr Client Troubleshooter' name='Btn760' ID='Button760'>
Add the following sub near the bottom, before </script>
' ConfigMgr Client Troubleshooter!
Sub Btn760_OnClick
compname = trim(document.frmMain.txtValue.value)
Set WShell = CreateObject("WScript.Shell")
Set fso = CreateObject("Scripting.FileSystemObject")
strSMSServerName = "ServerName"
strDMSourceFldr = "\\" & strSMSServerName & "\Remote$\"
strcmdending = "\\ServerName\Remote$\SCCMunHealthyClientTroubleShooter.hta & chr(34) & " -c: -h: -m:" & chr(34) & compname & chr(34) & " -a:1"
wShell.run chr(34) & strDMLocalFldr & strcmdEnding,1,vbfalse
End Sub
' gtk ends Client Troubleshooter!
Copy SCCMunHealthyClientTroubleShooter.hta to your Remote$ share.
Copy pskill.exe & psservice to your %windir% directory. latest pstools available from Windows Sysinternals
Edit SCCMunHealthyClientTroubleShooter.hta lines 21-25 with your values.
Const intMinDiskSpace = 2 '2 gb
Const strCCMSetupSource = "\\MYSCCMServer\sccmclient" 'path to ccmsetup.exe - ccmsetup.exe will be copied to the local system for install.
Const strCCMSetupArgs = "SMSSLP=mySLP FSP=myFSP" ' add appropriate server names
Const strClientVersion = "4.00.5931.0001"
Const strDefaultAdvertID = "LAB20083" 'enter default advertID for re-running mandatory assignments
Credit goes to MeenEnta (aka George K) for sharing the addons, see forum post here, Greg Ramsey for his Trouble-shooter Client.
-
-
Here is an add-on to Ron's Web Remote Tools page to check the a PC’s SMS Client Health state using Greg Ramsey’s SMS 2003 Client Troubleshooter, more details about this available here
Edit machrest.asp (take a back up, always better to be on the safe side) add the following around line 80ish or at the end of your other buttons, <input style='WIDTH: 180px' type='button' value='Client Troubleshooter' name='Btn747' ID='Button747'>
Add the following sub near the bottom, before </script>
' Client Troubleshooter!
Sub Btn747_OnClick
compname = trim(document.frmMain.txtValue.value)
Set WShell = CreateObject("WScript.Shell")
Set fso = CreateObject("Scripting.FileSystemObject")
strSMSServerName = "ServerName"
strDMSourceFldr = "\\" & strSMSServerName & "\Remote$\"
strcmdending = "\\ServerName\Remote$\unhealthyClientTroubleShooter.hta" & chr(34) & " -c: -h: -m:" & chr(34) & compname & chr(34) & " -a:1"
wShell.run chr(34) & strDMLocalFldr & strcmdEnding,1,vbfalse
End Sub
' gtk ends Client Troubleshooter!
Copy unhealthyClientTroubleShooter.hta to your Remote$ share.
Copy folder Systinternals (includes pskill.exe & psservice) to your Remote$ share. Latest pstools available from Windows Sysinternals
Edit unhealthyClientTroubleShooter.hta lines 23-26 with your values.
Const strCCMSetupSource = "\\ServerName\SMSClient\i386\" 'this location contains ccmsetup.exe and client.msi
Const strCCMSetupArgs = "SMSSITECODE=AUTO DISABLECACHEOPT=TRUE SMSCACHESIZE=1500"
Const strClientVersion = "2.50.4253.3000" ' update this version to you corporate standard version
Const strDefaultAdvertID = "XXXXXXX" 'enter the default advert to run with 'rerun advertisement'
Credit goes to MeenEnta (aka George K) for sharing the addons, see forum post here, Greg Ramsey for his Troubleshooter Client.
-
-
Here is an add-on to Ron's Web Remote Tools page to find the PC’s uptime since its last boot up on a given machine, it will prompt you for the machine name, then open up notepad and display similar to “\\PCNAME has been up for: 0 day(s), 2 hour(s), 9 minute(s), 1 second(s)”
Edit machrest.asp (take a back up, always better to be on the safe side) add the following around line 80ish or at the end of your other buttons, <input style='WIDTH: 180px' type='button' value='PC uptime since last boot' name='Btn745' ID='Button745'>
Add the following sub near the bottom, before </script>
' upTime since last boot!
Sub Btn745_OnClick
compname = trim(document.frmMain.txtValue.value)
Set WShell = CreateObject("WScript.Shell")
set fso = CreateObject("Scripting.FileSystemObject")
strSMSServerName = "ServerName"
strDMSourceFldr = "\\" & strSMSServerName & "\Remote$"
strcmdending = "\\ServerName\Remote$\uptime.bat" & chr(34) & " -c: -h: -m:" & chr(34) & compname & chr(34) & " -a:1"
wShell.run chr(34) & strDMLocalFldr & strcmdEnding,1,vbFalse
End Sub
' gtk ends upTime since last boot!
Copy uptime.bat (edit and add your server details) & uptime.exe to your Remote$ share.
Credit goes to MeenEnta (aka George K) for sharing the addons, see forum post here
-
-
Here is an add-on to Ron's Web Remote Tools page to list all the running processes on a given machine, it will prompt you for the machine/IP details, then open up excel and enumerate all the running processes.
| Image Name | User Name | Mem Usage |
| AppleMobileDeviceService.exe | SYSTEM | 4,028 k |
| avgrsx.exe | SYSTEM | 59,844 k |
| avgtray.exe | SYSTEM | 5,036 k |
| avgwdsvc.exe | SYSTEM | 2,552 k |
Edit machrest.asp (take a back up, always better to be on the safe side) add the following around line 80ish or at the end of your other buttons, <input style='WIDTH: 180px' type='button' value='List Running Processes' name='Btn749' ID='Button749'>
Add the following sub near the bottom, before </script>
Sub Btn749_OnClick
compname = trim(document.frmMain.txtValue.value)
Set WShell = CreateObject("WScript.Shell")
set fso = CreateObject("Scripting.FileSystemObject")
strSMSServerName = "ServerName"
strDMSourceFldr = "\\" & strSMSServerName & "\Remote$\"
strcmdending = "\\ServerName\Remote$\ProcessInfo.vbs" & chr(34) & " -c: -h: -m:" & chr(34) & compname & chr(34) & " -a:1"
wShell.run chr(34) & strDMLocalFldr & strcmdEnding,1,vbfalse
End Sub
Copy ProcessInfo.vbs to your Remote$ share.
Download ProcessInfo rename to .vbs
Credit goes to MeenEnta (aka George K) for sharing the addons, see forum post here
-
-
Came across this excellent blog post for troubleshooting SMS issues, its helped me out so many times, as I can never find it, adding it so its always available and I can find it easily, some of the same techniques apply to SCCM.
The main feature of this post I use and always recommend is as follows:
The following registry value will point to the inventory temp directory:
- HKLM\Software\Microsoft\SMS\Mobile Client\Inventory ----> "Temp Directory".
- Examples:
- 1. To save off inventory reports on a client that is not also an MP, create the following file:
- %systemroot%\system32\ccm\inventory\temp\archive_reports.sms
- 2. To save off inventory reports on a client that is also an MP, create the following file:
- <x>:\sms_ccm\inventory\temp\archive_reports.sms
- The XML file will be saved in the inventory\temp folder.
Note: Delete the archive_reports.sms file when you are done trouble-shooting.
-
Open up the inventoryagent.log from %systemroot%\system32\ccm\logs
-
Perform a full hardware inventory scan via SCCM Client Centre - Client Actions drop down list - HW Inventory (full) or the Right Click Tools
-
Wait for the HINV to complete by monitoring the inventoryagent.log, if you see examples like "Collection: Class "SMS_ActiveSyncService" does not exist out. InventoryAgent" - this is fine, just means the class doesnt exist on that machine and can safely be ignored.
-
Once it completes should see along the lines of Task Completed (cant quite recall the exact words).
-
In this folder "%systemroot%\system32\ccm\inventory\temp" you should now have an xml file which you can view to see if any data is being pulled back by the clients.
It all sounds long winded but it will help to identify if the issue is with the clients or the MP.
You can read all the other logging options here, credit goes to Russ Slaten.
http://blogs.msdn.com/rslaten/archive/2006/03/14/SMS-2003-Logging.aspx
-
-
After reading all the reviews on Ron Crumbaker’s Web Remote Tools and especially having a nice quiet period during the Christmas and new years holidays 
, I decided to set this up.
Thought I would add all the customizations I could find in 1 place, in the event someone else decides to set it up, there are a large number of customizations floating around on different blogs, making it sometimes a bit difficult to find, so here goes. Credit goes out to others, just adding there blogs to 1 place.
First of all, the original instructions for installing can be found here then there is the version for "Installing on Server 2008 with ConfigMgr 07" which can be found here, between these 2 sets of instructions you should be good to go to get up and running with the basic install.
Now for the fun part, the customizations that are out there, the possibilities are endless :) Here is an example of what can be done. If there are any in the example that have not been blogged about, let me know, I'll see what I can do for you.
Sherry Kissinger’s blog has a large number of them.
Brian Leary’s instructions on adding mouse hover tips – very cool.
If you have any that you have blogged about, created for your environment, let me know so I can link to your blog or add it to my blog for others to share.
Update: Ron's Web Remote Tools Customizations now has its own WIKI page.