myITforum.com Community Forum myITforum.com Community Forum

Home  Forums  Blogs  Live Support chat  Search Articles  Wiki  FAQ  Email Lists  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Photo Gallery  Member List  Search  Calendars  FAQ  Ticket List  Log Out

All Forums RSS Feed Subscription:


  


RE: Client Health Script

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
  Printable Version
All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> RE: Client Health Script Page: <<   < prev  1 [2]
Login
Message << Older Topic   Newer Topic >>
RE: Client Health Script - 10/30/2007 1:39:09 PM   
quietsoul

 

Posts: 30
Score: 0
Joined: 4/3/2007
Status: offline 		This script seems to work; however, I do not know why (maybe it's me) the SMS Client got installed on the workstations and it's available in the Add/Remove Programs. And looking at the script output, I got error stating that the workstation already has a client in it. here's more detail:


Property(S): ConfigDialog_InvalidSiteCode = The site code you have entered is not valid
Property(S): InstallDialog_Title = Install
Property(S): InstallDialog_SubTitle = The product is now ready to install
Property(S): InstallDialog_Info = Click Next to proceed.
Property(S): InstallDialog_Warning = WARNING: Installing the advanced client on this computer may cause the Windows Management Instrumentation (WMI) and Background Intelligent Transfer Service (BITS) services to stop and restart.
Property(S): ProgressDialog_Title = Please Wait
Property(S): ProgressDialog_SubTitle = Setup is configuring your system.
Property(S): CompleteDialog_Title = Setup Complete
Property(S): CompleteDialog_SubTitle = Setup has finished updating your system.
Property(S): CompleteDialog_Info = The SMS Advanced Client setup was successful.
Property(S): UserExitDialog_Title = Setup Aborted
Property(S): UserExitDialog_SubTitle = Setup was cancelled
Property(S): UserExitDialog_Info = The SMS Advanced Client setup was cancelled.
Property(S): InstallErrorDialog_Title = Setup Aborted
Property(S): InstallErrorDialog_SubTitle = Setup failed
Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue.
Property(S): bin.9180931B_6ABA_475F_8007_1211E0D725BA = C:\WINDOWS\system32\CCM\core\bin\
Property(S): core.9180931B_6ABA_475F_8007_1211E0D725BA = C:\WINDOWS\system32\CCM\core\
Property(S): SMSSITECODE = AUTO
Property(S): SmsMigrateInventory_ActionText = Migrating SMS Legacy Client inventory settings
Property(S): Inventory.BB910E4A_558A_418B_B3A0_1BACF5F45DDC = C:\WINDOWS\system32\CCM\Inventory\
Property(S): Temp.BB910E4A_558A_418B_B3A0_1BACF5F45DDC = C:\WINDOWS\system32\CCM\Inventory\Temp\
Property(S): FileColl.BB910E4A_558A_418B_B3A0_1BACF5F45DDC = C:\WINDOWS\system32\CCM\Inventory\Temp\FileColl\
Property(S): idmifs.BB910E4A_558A_418B_B3A0_1BACF5F45DDC = C:\WINDOWS\system32\CCM\Inventory\idmifs\
Property(S): badIDMifs.BB910E4A_558A_418B_B3A0_1BACF5F45DDC = C:\WINDOWS\system32\CCM\Inventory\idmifs\badmifs\
Property(S): noidmifs.BB910E4A_558A_418B_B3A0_1BACF5F45DDC = C:\WINDOWS\system32\CCM\Inventory\noidmifs\
Property(S): badNoIDMifs.BB910E4A_558A_418B_B3A0_1BACF5F45DDC = C:\WINDOWS\system32\CCM\Inventory\noidmifs\badmifs\
Property(S): Metering.A3E6C678_CFA0_4AD2_BA27_3422ED1462DB = C:\WINDOWS\system32\CCM\Metering\
Property(S): Temp.A3E6C678_CFA0_4AD2_BA27_3422ED1462DB = C:\WINDOWS\system32\CCM\Metering\Temp\
Property(S): SmsUninstallPrepDrvr_ActionText = Uninstalling Software Metering PREP Driver
Property(S): SmsInstallPrepDrvr_ActionText = Installing Software Metering PREP Driver
Property(S): SmsMigrateSwDistExecutionHistory_ActionText = Migrating Software Distribution History
Property(S): SmsSwDistSetCacheConfig_ActionText = Configuring Software Distribution Cache
Property(S): SmsRemoveUIEvents_ActionText = Removing UI Events
Property(S): SmsMigrateDownloadSchema_ActionText = Migrating download schema
Property(S): WindowsFolder.8AE6A59B_5597_4D75_9BFD_7F566BF56500 = C:\WINDOWS\
Property(S): SmsSoftwareDistributionCache.8AE6A59B_5597_4D75_9BFD_7F566BF56500 = C:\WINDOWS\system32\CCM\Cache\
Property(S): SmsStopUIComponents_ActionText = Stopping UI Components
Property(S): SmsRemoteToolsAllowed = 1
Property(S): KBSTUFF.98C5B086_7EB0_422A_B0A8_674010F525CD = C:\WINDOWS\system32\CCM\clicomp\RemCtrl\KBSTUFF\
Property(S): RemCtrl.98C5B086_7EB0_422A_B0A8_674010F525CD = C:\WINDOWS\system32\CCM\clicomp\RemCtrl\
Property(S): clicomp.98C5B086_7EB0_422A_B0A8_674010F525CD = C:\WINDOWS\system32\CCM\clicomp\
Property(S): help.98C5B086_7EB0_422A_B0A8_674010F525CD = C:\WINDOWS\system32\CCM\clicomp\RemCtrl\help\
Property(S): Res1033.754ED406_3093_4B9E_BD1B_3B4F9EEF31BA = C:\WINDOWS\system32\CCM\1033\
Property(S): Res1033.0EACD2EE_412B_4985_9727_96BC217AABD8 = C:\WINDOWS\system32\CCM\1033\
Property(S): RemCtrl1033.04505A0E_D569_4F61_A458_AB875F52A091 = C:\WINDOWS\system32\CCM\clicomp\RemCtrl\1033\
Property(S): help1033.04505A0E_D569_4F61_A458_AB875F52A091 = C:\WINDOWS\system32\CCM\clicomp\RemCtrl\help\1033\
Property(S): Res1033.04505A0E_D569_4F61_A458_AB875F52A091 = C:\WINDOWS\system32\CCM\1033\
Property(S): ProductState = 1
Property(S): REINSTALLMODE = vmaus
Property(S): CCMHTTPPORT = 80
Property(S): CURRENTDIRECTORY = C:\WINDOWS\system32
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 1328
Property(S): PRODUCTLANGUAGE = 1033
Property(S): VersionDatabase = 110
Property(S): VersionMsi = 3.01
Property(S): VersionNT = 501
Property(S): WindowsBuild = 2600
Property(S): ServicePackLevel = 2
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\WINDOWS\TEMP\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\WINDOWS\system32\config\systemprofile\Application Data\
Property(S): FavoritesFolder = C:\WINDOWS\system32\config\systemprofile\Favorites\
Property(S): NetHoodFolder = C:\WINDOWS\system32\config\systemprofile\NetHood\
Property(S): PersonalFolder = C:\WINDOWS\system32\config\systemprofile\My Documents\
Property(S): PrintHoodFolder = C:\WINDOWS\system32\config\systemprofile\PrintHood\
Property(S): RecentFolder = C:\WINDOWS\system32\config\systemprofile\Recent\
Property(S): SendToFolder = C:\WINDOWS\system32\config\systemprofile\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\WINDOWS\system32\config\systemprofile\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\WINDOWS\system32\config\systemprofile\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 15
Property(S): PhysicalMemory = 510
Property(S): VirtualMemory = 1150
Property(S): AdminUser = 1
Property(S): LogonUser = SYSTEM
Property(S): UserSID = S-1-5-18
Property(S): UserLanguageID = 1033
Property(S): ComputerName = ADSTUDIODEV
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1280
Property(S): ScreenY = 1024
Property(S): CaptionHeight = 26
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 13:35:59
Property(S): Date = 10/30/2007
Property(S): MsiNetAssemblySupport = 2.0.50727.42
Property(S): MsiWin32AssemblySupport = 5.1.2600.3019
Property(S): RedirectedDllSupport = 2
Property(S): Privileged = 1
Property(S): USERNAME = DOIT
Property(S): COMPANYNAME = GMU
Property(S): DATABASE = C:\WINDOWS\Installer\5789.msi
Property(S): OriginalDatabase = C:\WINDOWS\system32\ccmsetup\{2FBB7E06-7665-442B-98E3-189CB634C5CC}\client.msi
Property(S): UILevel = 2
Property(S): QFEUpgrade = 1
Property(S): Preselected = 1
Property(S): ACTION = INSTALL
Property(S): SMSPREFERREDCLIENT = Remote
Property(S): ISIA64 = FALSE
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 0
Property(S): SOURCEDIR = C:\WINDOWS\system32\ccmsetup\{2FBB7E06-7665-442B-98E3-189CB634C5CC}\
Property(S): SourcedirProduct = {4A39A27F-005B-407E-8CF5-F4D8065658E4}
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): INSTALLLEVEL = 1
MSI (s) (C4:44) [13:35:59:477]: Cleaning up uninstalled install packages, if any exist
MSI (s) (C4:44) [13:35:59:477]: MainEngineThread is returning 1603
MSI (s) (C4:DC) [13:35:59:573]: Destroying RemoteAPI object.
MSI (s) (C4:4C) [13:35:59:573]: Custom Action Manager thread ending.
=== Logging stopped: 10/30/2007  13:35:59 ===
MSI (c) (30:14) [13:35:59:573]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (30:14) [13:35:59:573]: MainEngineThread is returning 1603
=== Verbose logging stopped: 10/30/2007  13:35:59 ===

(in reply to bwilms)
Post #: 51
RE: Client Health Script - 10/30/2007 1:46:32 PM   
bmason505

 

Posts: 1983
Score: 104
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline 		It should only install if the client is broken somehow.  Did you check the log it created when run?  Did you configure everything in the script to your environment and servers, etc.?

_____________________________

Brian Mason
MCSA\MCSE\MS MVP - SCCM
Wells Fargo
http://www.miscusergroup.org/

(in reply to quietsoul)
Post #: 52
RE: Client Health Script - 10/30/2007 1:48:11 PM   
quietsoul

 

Posts: 30
Score: 0
Joined: 4/3/2007
Status: offline 		yep, I have configured everything in the script pertaining to my environment. One thing i noticed is that when I put it on the startup script, it did not work properly. It went and install a version which is corrupted, and made available on Add/Remove Programs. Now, when I execute it manually, it works like a charm without any error.

(in reply to bmason505)
Post #: 53
RE: Client Health Script - 10/30/2007 2:51:57 PM   
quietsoul

 

Posts: 30
Score: 0
Joined: 4/3/2007
Status: offline 		nevermind, I got it to work. Script works great! thank you for your hard work!

(in reply to quietsoul)
Post #: 54
RE: Client Health Script - 10/30/2007 3:03:49 PM   
hcortez463


Posts: 675
Score: 48
Joined: 4/8/2005
Status: offline 		when will the updated script with all the fixes be available?

_____________________________

If it Helps, Please rate....

(in reply to quietsoul)
Post #: 55
RE: Client Health Script - 10/30/2007 3:42:40 PM   
bmason505

 

Posts: 1983
Score: 104
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline 		Uploaded version 4.9.

_____________________________

Brian Mason
MCSA\MCSE\MS MVP - SCCM
Wells Fargo
http://www.miscusergroup.org/

(in reply to hcortez463)
Post #: 56
RE: Client Health Script - 10/30/2007 4:10:10 PM   
mhudson

 

Posts: 509
Score: 10
Joined: 4/1/2007
From: College Station, TX
Status: offline 		Since you are installing the client why not force it to run the policy and inventory collections...

On Error Resume Next
Set oCPAppletMgr = CreateObject("CPApplet.CPAppletMgr")
Set oClientActions = oCPAppletMgr.GetClientActions()
For Each oClientAction In oClientActions
If oClientAction.Name = "Discovery Data Collection Cycle" Then
    oClientAction.PerformAction
  End If
  If oClientAction.Name = "Software Inventory Collection Cycle" Then
    oClientAction.PerformAction
  End If
  If oClientAction.Name = "Hardware Inventory Collection Cycle" Then
    oClientAction.PerformAction
  End If
  If oClientAction.Name = "Request & Evaluate Machine Policy" Then
     oClientAction.PerformAction
  End If
Next


_____________________________

Matthew Hudson
http://sms-hints-tricks.blogspot.com/
http://www.sccm-tools.com

(in reply to bwilms)
Post #: 57
RE: Client Health Script - 10/30/2007 4:30:21 PM   
bmason505

 

Posts: 1983
Score: 104
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline 		Trying to think of a downside to that.  We use it for rollouts too and since this will run at startup, and since users are likely to logon quite soon after, would it make sense to let the system cool for a bit so they don't feel so much lag at boot?  I don't think we're in any hurry; these things should all take place on their own within an hour.  If everyone started at the same time in the office and they were all doing inventory and such at the same time, I'd figure it'd slow things down there too.

Playing devil's advocate here.  Sell me on it.  What's an upside?


_____________________________

Brian Mason
MCSA\MCSE\MS MVP - SCCM
Wells Fargo
http://www.miscusergroup.org/

(in reply to mhudson)
Post #: 58
RE: Client Health Script - 10/30/2007 4:53:52 PM   
mhudson

 

Posts: 509
Score: 10
Joined: 4/1/2007
From: College Station, TX
Status: offline 		I realize that all these actions are peformed by the client at the post install phase.  It doesn't hurt the client.  If it already is processing the hw inventory or policy then it just ignores it.  Running the script causes no harm to the machine but if the machine didn't kick it off when it was suppose to then this become a re-inforcement of the necessary post install processes.

Otherwise...I bow down to your software ;)
Good job!!!

_____________________________

Matthew Hudson
http://sms-hints-tricks.blogspot.com/
http://www.sccm-tools.com

(in reply to bmason505)
Post #: 59
RE: Client Health Script - 11/6/2007 11:11:06 AM   
rbennett806


Posts: 786
Score: 13
Joined: 6/14/2006
Status: offline 		Brian,

I'm just now digging into this script (I finally made some "free" time), and I've got some comments/questions/enhancements/stuff...

1. Why not make the policy refresh talked about in this post an optional subroutine then? Something like "do_RUN_POLICY_REFRESH = True".
2. You might add in an additional comment to expand on this line (Line 118) "'Specify Site server to send good/success logs - will overwrite existing log file". My very first task was to make sure the log file got overwritten and not appended. Which I can easily find out, but it might save me 5 minutes if it was commented in the script And why have two different directories? Can't you just have a single folder for the log files and then name one "bad_sms_chk_XXXXX.log" and the other "good_sms_chk_XXXXX.log"?
3. Can you include some simple instructions for SMS admins to manually test the script to ensure that it's working fully in their environment? Before I deploy something to my machines (test or production) I always have to walk through it to make sure there's no glitch that will affect our specific environment.
4. Maybe you can put a supported OS list at the top of the script file? This would maybe help ease the concerns of management with using someone else's script.
5. Not a biggie, and I haven't dug too deeply just yet, but what about adjusting your logs to support SMS TRACE32.EXE as the viewer? That way you can easily highlight errors and warnings. I mean, right now it can be opened in it, but I just thought the additional ability to immediately locate an error might be worth something to new SMS admins.
6. Maybe along with the latest version number you could put a public release date? So that we know how old the script is. I know you put it up on the forum and such, but it might be a nice addition for when we're looking at our scripts in our own environment (it might be a reminder for us to go out and track down your stuff once in awhile to look for an update).
7. This doesn't really bother me, but would it be possible to make the configuration seciton stand out some more? I can see some admins that aren't used to VBScript getting a little overwhelmed, so it might be nice to make it easier on them to find the section that they have to modify. And would it be worth anything to add in a few comments for new SMS admins on how to locate some of the info needed? I mean, I would assume that they'd know how to get their site server and site code, but I thought I'd toss out the idea (I know a few that just jump right in and start tinkering).
8. Is there some way you cna get rid of the commented lines through the subroutines? There are some that look like I'd need to uncomment if I was doing something beyond the default, like "'If oClientComponent.DisplayName = "SMS Client Core Components" Then", and it might be nice not to have to scrounge through the script trying to figure out what that line does to see if I need it or not (that's just one example, there are a few small lines commented out here and there).

Okay, so now that I gushed out a bunch of items (I'm still poking around and testhing things of course), I think the script looks really good. I know this is your own baby, so don't take any of those comments the wrong way, I'm just lobbing things out there. Nice job on the script! Thanks for sharing this with the community.

(in reply to mhudson)
Post #: 60
RE: Client Health Script - 11/6/2007 2:12:49 PM   
Rickym61

 

Posts: 65
Score: 2
Joined: 4/4/2007
Status: offline 		Hmm, some good points above...look forward to the future releases.. Just read that the latest version, logs to the event log, must have missed this part...

you got to love this script, we have just upgraded all our SMS servers to SP3, this script is upgrading alot of clients for me already, despite me having a change to mass upgrade end of the month, hopefully by then, will have done most of them for me...thanks Brain & Rob

(in reply to rbennett806)
Post #: 61
RE: Client Health Script - 11/6/2007 2:45:12 PM   
bmason505

 

Posts: 1983
Score: 104
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline 		Great feedback, Rick and some good ideas.  All the thanks to "Rob & Brian" should include this group too because ideas bounced around here go into it.

Let me answer some questions quickly, and get back to you later on others.

1. Good idea to make it an option since I still don't get the need for instant policy, but can let the user decide.
2. We allow it to overwrite to save space, but it does get counted in the web background tool if you're running that.  I'll make the comment though.  Why two directories?  We separate our servers and workstations because two different groups support them.  They are the ones who actually look at the logs day to day.  And mostly, the just look at the repeaters.  If you see a machine has failed 5 days in a row, it'll fail the 6th too, so you're going to have to open the log and see what's going on.
3. I did mention how I would test it in the article:
quote:

...it's a good way for you to test the script and GPO before sending it to others; put some test machines in an OU and link the GPO to it. When you're satisfied, start rolling.
- so you can make a sub OU where your machines are, link the GPO to it, and drop some machines in there to test.  Test how?  Disable SMS and reboot is one way.
4. We're running the script on all OS that SMS 2003 supports.
5. I do use trace, but this format also lets you look at the application event log on the machine quite easily.
6. Can do.
7. We discussed this and even discussed making a GUI to make the entries.  But we figured that it's just so powerful as a GPO that we think the user should feel comfortable about editing and configuring this on his own before using it.
8. This kind of relates back to #7.  You can clean these yourself and if not sure, just ask.

I don't consider Rob & I to be the sole owners of this.  Obviously you can add or remove as needed and we welcome feedback like this.  And I'd love to hear of any client issue that we're not fixing.  In our environment of 100K  machines, this is pretty much doing the trick.


_____________________________

Brian Mason
MCSA\MCSE\MS MVP - SCCM
Wells Fargo
http://www.miscusergroup.org/

(in reply to Rickym61)
Post #: 62
RE: Client Health Script - 11/6/2007 5:36:17 PM   
rolson


Posts: 79
Score: 4
Joined: 6/4/2001
Status: offline 		This is certainly a consideration, keeping in mind our intent was for this to be a start up script and it needs to have the least amount of impact on the client and network as possible.

First -
Performing this action would force a policy refresh and inventory cycle which would have a majority of clients possibly sending inventory every morning.

Second -
If we just installed the client theres no need for this since it will happen on its own and you'll just be interfearing with the client sending up its first snapshot and it would be redundant since we are already smacking the client down.

However, I am not opposed to adding it as a feature option in the script, i'm sure there are many shops that could still benefit from this and whatever situation they might have that requires the need. But the client needs to be installed and functional for this and since we look for a healthy client and if so we exit then this wouldnt get hit. I do have some ways to make it run randomly every so many days or whatever.. I'm sure I can find a sweet spot to stick it into.

-- ok now I'll dig through the rest of the thread and see how far i shoved my foot in my my... ;) LOL

Thanks for the input!

-Rob

(in reply to mhudson)
Post #: 63
RE: Client Health Script - 11/6/2007 5:42:00 PM   
rolson


Posts: 79
Score: 4
Joined: 6/4/2001
Status: offline 		thats awesome Rick, glad its helping, thats exactly what we want it to do!

-Rob

(in reply to Rickym61)
Post #: 64
RE: Client Health Script - 11/6/2007 6:41:18 PM   
rolson


Posts: 79
Score: 4
Joined: 6/4/2001
Status: offline 		Woow.. lots of feedback, this is great!

1. will consider and see how we can integrate ( see my previous post about this)

2. it always overwrites, as this contributes to the counting/tracking that the web app portion does - but we can add more comments to say it does.

3. I am working on a regular helpfile ( CHM) to be released soon as I have time to finish, we were hoping for this kind of input from the community so we can make the script and docs more solid for every, so all this input really helps us get things cleaned up and address what different users might run into so we can have a universal script that will work in 99% of shops if possible.

4. There are actually 2 health scripts we personally use, we've broken the server client script away from the workstation script so theres no confusion, I'll be posting a server script soon.. I didnt want to manage 1 sets of code, but we are seeing a need to to seperate the 2. So we'll also put info about supported platforms

5. You can already open in Trace.. they are .log files, however the loggin doesnt clearly say ERROR or WARNING etc.. I think we can work that in so those automatically get highlighted... but also keep in mind we forward the log the to application event log now too so you can more easily troubleshoot clients without haveing to search thier systems for the logs or find them on the logging server.
The format of the log was intended to be "eye friendly" and to make it easy to parse up for the web reporting stuff. I personally hardly ever look at them, I look at the web report to tell me whats going on, then if I really need to troubleshoot the client I go directly to the application event log on the system.

6. Will add, no problem... you can also download from www.dudeworks.com , when you do, you can subscribe to the download folder and then when we make future updates and additions you will automatically get an email stating the update.

7.yes we an do that.

8. Well yes and no, those are there as an option, if commented out then the script is just reporting the status for that component, if uncommented then its performing actions..  - what I'm going to do in a next version is add the option to select whether you to jus report the issue and/or also perform the actions. This way you dont need to look at anything below the config section ever.

All great suggestions and input!!!

one last thing about what brian posted as for this being an open source script, it is very much so, and everyone is free to do with it what they want that was our intention ( partially) --
What we really want for the community I think is to have a single( if possible) solution that anyone can use and put to work immediately,  having20 versions of it running around will make that very hard, it will also kill peoples confidence in the script and its use since they will question which one is best and so on, and thats ok with me but I'd for to be the guys trying to implement them all til he found which worked. With that said have it, pick it apart, or work with us to contribute to the single solution and we can just start adding credits to the script so all the contributors get some kudos and from this side brian and I can moderator and quality control( did I say that.. omg ) of the script to make sure anything added actually works and contributes to the script.

So bring on your ideas.

-Rob

(in reply to rbennett806)
Post #: 65
RE: Client Health Script - 12/6/2007 10:21:33 AM   
hcortez463


Posts: 675
Score: 48
Joined: 4/8/2005
Status: offline 		Brian
I have been testing your latest script and it is still installing the client if it detects the client being stopped.  Just wanted to updated u on this..

_____________________________

If it Helps, Please rate....

(in reply to bmason505)
Post #: 66
RE: Client Health Script - 6/19/2008 3:30:06 PM   
hcortez463


Posts: 675
Score: 48
Joined: 4/8/2005
Status: offline 		Brian
Any updates to the script?

_____________________________

If it Helps, Please rate....

(in reply to bmason505)
Post #: 67
RE: Client Health Script - 6/19/2008 4:52:22 PM   
bmason505

 

Posts: 1983
Score: 104
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline 		The latest is on Dudeworks and should have it.  If it doesn't, just private message me.  I'm pretty sure the last version simply enabled and started ccmexec.

_____________________________

Brian Mason
MCSA\MCSE\MS MVP - SCCM
Wells Fargo
http://www.miscusergroup.org/

(in reply to hcortez463)
Post #: 68
RE: Client Health Script - 8/7/2008 1:00:14 PM   
sringler

 

Posts: 16
Score: 0
Joined: 5/29/2002
Status: offline 		Brian,
I just looked at the latest script  (4.11) but I'm a little bit confused. As far as I can see, all the "Run Client Stupid Healing Tasks" don't start as long as the client passes the  CCMEXEC Check. I would like the script to check the BITS service for example but the scripts quits before the Check begins..so this doesn't make sense to me. Would you just explain it a little bit more to me, why the other checks only run if clientstate=1 after the ccmexec check.
Thanks
Stefan

(in reply to bmason505)
Post #: 69
RE: Client Health Script - 8/7/2008 1:54:41 PM   
rolson


Posts: 79
Score: 4
Joined: 6/4/2001
Status: offline 		You can modify to your need, just add a call to the BITS check prior to the "stupid healing tasks".. this will include BITS in the pre-checks.
note: this area is a little messy in the script and not clearly defined, I have a new rev in the works( i know, know.. been promising for a while.. but its coming)... the new rev will make selecting your pre and post checks much easier and clear.


CHK_SMSVERSION

if do_CHK_AUTOUPDATE = true then CHK_AUTOUPDATE      
if do_CHK_CCMEXEC = true then CHK_CCMEXEC 
if do_CHK_SMSUPDATECLIENT = true Then CHK_SMSUPDATECLIENT      
if do_CHK_SYSTEMPATH = true then CHK_SYSTEMPATH
if do_CHK_BITS_SERVICE = true then CHK_BITS_SERVICE 

_____________________________

Rob Olson
rob@dudeworks.com
www.dudeworks.com/inventorymanager

(in reply to sringler)
Post #: 70
RE: Client Health Script - 8/8/2008 3:59:12 AM   
sringler

 

Posts: 16
Score: 0
Joined: 5/29/2002
Status: offline 		Thanks Rob,
looking forward to see the new version!


(in reply to rolson)
Post #: 71
RE: Client Health Script - 9/29/2008 9:30:50 AM   
Yanze


Posts: 24
Score: 0
Joined: 4/2/2007
Status: offline 		I'm trying to register myself on the DudeWorks website, but the confirmation email isn't coming.
Is the latest version of this script downloadable somewhere else on the internet?

(in reply to sringler)
Post #: 72
RE: Client Health Script - 9/29/2008 9:30:51 AM   
Yanze


Posts: 24
Score: 0
Joined: 4/2/2007
Status: offline 		I'm trying to register myself on the DudeWorks website, but the confirmation email isn't coming.
Is the latest version of this script downloadable somewhere else on the internet?

(in reply to sringler)
Post #: 73
RE: Client Health Script - 9/29/2008 10:40:15 AM   
Rickym61

 

Posts: 65
Score: 2
Joined: 4/4/2007
Status: offline 		The same was happening for me, took a while for the email to come through but it did in the end.

removed the script that I attached (sherry twists your arm really hard  ) 

< Message edited by Rickym61 -- 9/29/2008 12:10:25 PM >

(in reply to Yanze)
Post #: 74
RE: Client Health Script - 9/29/2008 11:25:38 AM  1 votes
skissinger


Posts: 1976
Score: 129
Joined: 9/13/2001
From: Sherry Kissinger
Status: offline 		I asked the Dude offline; it looks like the email address entered was invalid?  Perhaps you accidentally misspelled your email?  If you try again and double-check your email address, it should work automagically correctly.

Ricky, could you remove the attachment?  I believe they are trying to keep version control under control--at least as much as possible.  If it's posted here, it might take on a life of it's own...

Edit:  Virtual arm-twisting half-way around the world works wonders.  It can get people with great ideas to share them. 

< Message edited by skissinger -- 10/1/2008 5:36:43 AM >

_____________________________

mofmaster@smsexpert.com (version 2007) | http://www.smsexpert.com | http://www.sccmexpert.com
Microsoft MVP - ConfigMgr

(in reply to Rickym61)
Post #: 75
RE: Client Health Script - 9/29/2008 11:27:03 AM   
rolson


Posts: 79
Score: 4
Joined: 6/4/2001
Status: offline 		Your email is bouncing, registration works fine if its a valid email address you'll recieve the confirmation, thats why theres a confirmation. Even then it doesnt stop people from registering with bogus info  ;)

_____________________________

Rob Olson
rob@dudeworks.com
www.dudeworks.com/inventorymanager

(in reply to Yanze)
Post #: 76
RE: Client Health Script - 10/1/2008 4:10:35 AM   
Yanze


Posts: 24
Score: 0
Joined: 4/2/2007
Status: offline 		Thanks, I got the email and now it works :)

And the script already does its job!

(in reply to rolson)
Post #: 77
Page:   <<   < prev  1 [2]
All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> RE: Client Health Script Page: <<   < prev  1 [2]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll