Chris Stauffer at myITForum.com

Thanks John for sharing this info

http://myitforum.com/cs2/blogs/jmarcum/archive/2008/07/01/119242.aspx

Chris Stauffer <><

I and several others have had an issue with the temp DB growing out of control and not auto shrinking as it should.

 After having a discussion on the emial group the other week we cam up with a possible solution thanks to Jim Bezdan.

 Here is the solution:

**************************************************

On Ron's web console we had an issue since we have a mix of 2kpro and XP machines.This replacement code for the Remote control button will check to see what version the OS is on the system that you want to remote into then use the appropriate executable for the OS. Just replace the old code in the Machrest.asp file with this code 

'************************

' Remote Control Button *

'************************

' Original Code

' Sub Btnl_OnClick

'

'             Dim CompName,oWshShell

'             CompName = Trim(document.frmMain.txtValue.value)

'             If len(Trim(CompName)) = 0 then

'                         MsgBox "Please type a Machine Name.",,"SCCM 2007 Remote Control"

'             Else

'                         Set oWshShell = CreateObject("WScript.Shell")

'                         path = "\\OASCCM01\remote$\rc.exe"

'                               oWshShell.run path & " 1 " & CompName & " \\OASCCM01\"

'             End If

' End Sub

'New Code

Sub Btnl_OnClick

            On error resume Next

            Dim CompName,oWshShell

            CompName = Trim(document.frmMain.txtValue.value)

            If len(Trim(CompName)) = 0 Then

                        MsgBox "Please type a Machine Name.",,"SCCM 2007 Remote Control"

            Else

                        Set objPing = GetObject("winmgmts://" & ServerName & "/root/default:PingPoller")

                        objPing.Ping CompName, "100", "1", PingResult

                        if PingResult <> 0 Then

                        MsgBox "Machine did not respond to ping.",,"Current Loggod on User"

                        Else     

                                    Set objSWbemServices = GetObject("winmgmts:\\" & CompName & "\root\cimv2")

                                    err.clear

                                    Set colSWbemObjectSet = objSWbemServices.ExecQuery("Select * FROM Win32_OperatingSystem")

                                    For Each objSWbemObject In colSWbemObjectSet

                                    StrOS= objSWbemObject.Version

                                    Next

                        end If

            end If

            If StrOS = "5.0.2195" Then

                        Set oWshShell = CreateObject("WScript.Shell")

                        path = "\\OASCCM01\remote$\remote.exe"

                        'You will need to edit the following line to fit your environment.  SMSServer = Your SMS Server Name

                          oWshShell.run path & " 2 " & addresses(ubound(addresses)) & " \\OASCCM01\",0,False

                         Else

            Set oWshShell = CreateObject("WScript.Shell")

            path = "\\OASCCM01\remote$\rc.exe"

             oWshShell.run path & " 1 " & CompName & " \\OASCCM01\"

            end If

End Sub

For more info on using the remote tool at command line review this:  http://technet.microsoft.com/en-us/library/bb681027(TechNet.10).aspx

 Here is a new Version. not much has changed since the 1.4 version but this should be more stabel and it has some added Mini Mof Additions

Changes 

• Added Local Share/ Printer and Admin tracking
• Added SQL 2005
• Added MDAC
• Added Support for Mcafee 8.5
• Fixed Issue with DPW and DOH tracking
  

I last updated this in January but never got around to posting it (Sorry bin buisy with ConfigMgr 2007)

Chris Stauffer 

 Sorry for the quick release between versions but i needed to address a few changes quickly so enjoy this new version

******************************************************************************************************************************************** 

One of the big complaints that I heard at MMS 2008 during the Client Health Check breakout  (by Paul Thomsen) was that most solutions require yet another product and client. A key part of Microsoft’s solution (discussed in Paul’s session) is a tool by 1E . 1E uses their 1E Wakeup tool to monitor the client’s health when the Wakeup service isn’t being used.

 Unfortunately some of us can not afford to purchase everything we need to get ConfigMgr up and running, let alone another product. While the 1E Client Health features are beneficial, due to budgetary restraints some people cannot go that route just yet. So this is simply a free solution that can get you moving in the right direction. The direction being a more healthy ConfigMgr environment.

 
This tool will check the health of a client from the machine itself instead of from the server or collections. It is to be used in addition to the Client Health Checks. I will be updating the checks once I have SCCM Deployed in production.

So I was thinking what if instead of a service that runs all the time why not just have a task sequence that fires off once or twice a day. This would allow you to do the same check without having to have something running all the time. So I created a script that will create a Scheduled task that will trigger a script to scan the system for problems.

This solution is meant for SCCM 2007 client but the script could be altered to use it on SMS 2003 as well.

Please read attached doc for full explination of how this works.

Note: this Script is very complex so I may have missed some things that it does. If so let me know and I will add it to the description.

Note: all executable files have been renamed so that they can get though virus scanners without being striped so make sure that you rename things.

This application includes the following:

• check.mof
• This can be added to the Configuration.mof for tracking the usage of this toll in SCCM
• Client_Health_Check.ipf
• This is the SMS installer Script to allow you to make changes to the scripts before you compile it and deploy it to you clients
• Client_Health_Check_Local.doc
• This Document
• Create_Task.vbs
• The script to create the Scheduled Task that will fire the Health Check task Script
• Health_Check.reg
• Just an example of the Reg keys that are created by the Script
• Health_Check.vbs
• The Script that will do all of the health checks and attempt to repair issues if you have any.

Please feel free to make any changes that you find necessary. If you make changes that are to fix bugs or make the script better as a whole please share them with me so I can release a new version for everyone to use.

Special Thanks To the following For code snippets:

• 1E And Richard Threlkeld  For the original Health Check tool
• David Turner For cache expander Function
• DudeWorks For script functions from their original Health Check scripts
• Sherry Kissinger For Error checking And Function editing
• Authors of SMS 2003 Recipes (a must have book For any SMS admin)
• My beta testers. I’ve been asked by some to not mention there names so I will not.
• The rest know who they are and I will gladly give them recognition if they want it.
• The guys and gals on the MyITForum MSSMS list For chiming in when needed
• And anybody else that added their 2 cents :-)

Thanks

Chris Stauffer <><

New Version released

http://myitforum.com/cs2/blogs/cstauffer/archive/2008/06/13/client-health-check-script-and-scheduled-task-version-1-1-release.aspx

Thanks Chris Stauffer <>< 

At my job we Audit Remote Control so that if someone is somewhere they are not suppose to be there is a trail and proof.

I used John Nelson's tool to find the message codes I needed for SCCM

http://myitforum.com/cs2/blogs/jnelson/archive/2008/05/21/117428.aspx

Here are the Audit numbers for remote control functions in ConfigMgr 2007 SP1

The remote tools can be tracked by creating a new  "Status Filter Rules" for the event ID's listed below. Set the Action to:

• Report to the Event log
• Replicate to the Parent Site
• Replication Priority: Medium

Then we use a tool that tracks the event ID's that this generates on the Central site. Since Status messages are passed up to the parent site you only need to create the Status Filter Rules on the central site.

In SMS 2.0 and 2003 there where additional numbers to be audited but i do not see those numbers in 2007 because the remote tool doesnt have the smae functionality that the old Remote.exe had so the other audit numbers may not be needed but i have attached the list incase you find that you need it.

Chris Stauffer <><

 http://support.microsoft.com/kb/953649/en-us

Fix list

SMS Permissions matrix

http://myitforum.com/cs2/blogs/jnelson/archive/2008/05/30/117881.aspx

SCCM Permissions Matrix

http://myitforum.com/cs2/blogs/jnelson/archive/2008/05/30/117883.aspx

 I seriously want one of these babies but i think i will wait for the price to lvl out 

http://promotions.newegg.com/crucial/052108/index.html?nm_mc=EMC-IGNEFL053008&cm_mmc=EMC-IGNEFL053008-_-MECH-_-EB3A-_-CrucialSSD

 WOW Check out the G factor on these babies. How to you reach a G of 1500 ? 

 General
Brand     Crucial
Model     CT64GBFAA0
Device Type     External Solid state disk (SSD)
Expansion / Connectivity
Form Factor     2.5"
Capacity     64GB
Interface Type     SATA
Performance
Max Shock Resistance     1500G
Max Vibration Resistance     20G
Sequential Access - Read     up to 100MB/s
Sequential Access - Write     up to 35MB/s
MTBF     2,000,000 hours

More Reading on the product

http://images.crucial.com/pdf/spec_sheets/crucial-ssd.pdf

 I put together directions for Our Admin to install SP1. I wanted to share them. 

I wanted to make it so that all you had to do was run a comand line to do the install but apparently the Config Manager 2007 Sp1 Documents do not contain direction for doing this or atleast they have not been released yet.

Anyway enjoy.

AI and AIS are two completely separate products.

AI - An integral feature set of Configuration Manager, that appears as a node of the SCCM admin UI. AI is built into Configuration Manager and does not cost any additional money or have any additional requirements. You will be able to get occasional bulks updates from Microsoft, as they did for SMS 2003 SP3 (current planned frequency is every 6 months). These will not be pushed down to you, but rather you would need to go to Microsoft site and download a large MSI package (like a service pack).

AI Plus - AI Also has an additional "feature" for Software Assurance customers, the Sync Point ‘connector' to System Center Online. If you are an SA customer you need to contact your TAM or sales person and get a cert.pfx from Microsoft. Once you get the certificate, you'll be able to deploy the sync role and get automatic downloads of catalog updates from Microsoft. Current planned update frequency is about 2 weeks. You ALSO have the ability to submit titles to Microsoft and have them researched.

AIS - an online service with an individual agent that is deployed by an MSI package and connects to an online website via the web agent. First you deploy a msi file (program) to all of your machines. Then the machines send information directly to Microsoft. It is a 100% online resource.  You go to web site and run reports. It is 100% online service. It has nothing to do with SCCM. This is for smaller customers that do not deploy Configuration Manager.

Large Enterprises would not want to use this service because they would not want all of their machines uploading inventory to Microsoft across the WAN, or deploy another agent.

AI and AIS have nothing to do with each other except for one small detail, ultimately they are both based on the same "catalog" of information. The actual products have Nothing to do with each other. You can read more about this in this Forum post http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3397518&SiteID=17

Here is a link to the Post that talks about getting the cert http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3411685&SiteID=17

If you have any issues please post there and Dan will see it and assist them

Special Thanks to Todd Hemsell for providing this information

I needed a CCR creator tool for ConfigMgr 2007. It is based on the tool that was made for SMS 2003.  Download the attached zip and enjoy.

 Run the Create_and_copy.bat file and it will

1. Create a folder on the c drive called CCRBIN
2. Copy the IPF and Machines.cvs files to the CCRBin folder

Then it will ask you to comple the IPF with SMS installer.

Then to run it use thes directions

1. Add the machines that you want CCR's created for to the Machine.cvs file (it can be 1 or many)
2. Execute the EXE
    3. It will prompt you for your ConfigMgr Server
    4. Then it will prompt you for your ConfigMgr Site code
        (This info can be hardcoded just follow directions in the IPF to do that)


Created by Chris Stauffer

Based on the tool by Patrick Hoyt  for SMS 2003

 I am now a: Microsoft Certified Technology Specialist (MCTS): System Center Configuration Manager 2007, Configuration.

 Wow glad that weight is lifted 

I took the test today and was extatic with the results.

See it was worth going to MMS 2008 and focusing on Configuration Manager. 

Chris Stauffer <>< 

 I upgraded my Home system to XP Sp3 about a week ago and since then everytime i try and use my system this issues occurs. I can conferm that it is definatly Wuaueng.dll / SVCHost.exe. I used Process Explorer to find the dll that was taking 100% of my system. after i killed the DLL the system returned to normal.

I tried to reinstall the Windows Update client to version 3.0 and it did NOT fix the issue. And several of the other issues that i used when Windows update cause this problem with Sp2 but i was not able to resolve the problem.

Here is a link to a forum working to resolve the issue. 

http://www.broadbandreports.com/forum/r20453781-XP-Pro-Wuauengdll-Svchostexe-100-Usage-Problem

So be carefull if you plan on deploying this upgrade to your network because you will have your hands full again.

Updated:

More interesting info:

I have 3 different copies of wuaueng.dll on my system so what one is the newest one?

Why Does the DLL with the newest date  have the oldest  version number? 

Is this what is causing the problem?

wuaueng.dll Date: 4/14/2008 Version: 5.4.3790.5512

wuaueng.dll Date: 7/30/2007 Version: 7.0.6000.381

wuaueng.dll Date: 4/16/2007 Version: 7.0.6000.374

Chris Stauffer <><

 I have gotten a great response for the request for Beta testers especially from those of you with great scripting background. This is great since I know enough about scripting to be dangerous

I will hold off posting the names of those that have joined the group till later, I want to make sure that they are ok with me mentioning there name and I plan on doing a thank you blog to all involved once we move this from beta to public.

FYI incase anybody was wondering. This is a Community (Public) effort. I am not looking to make a profit from this effort. Simply i am trying to put together a solution that will work across environments.

 So thanks to all involved and hopefully we will have a great solution in a few weeks.

Chris Stauffer <>< 

Official Release available here

New Version released

http://myitforum.com/cs2/blogs/cstauffer/archive/2008/06/13/client-health-check-script-and-scheduled-task-version-1-1-release.aspx

Thanks Chris Stauffer <><

New Version released

http://myitforum.com/cs2/blogs/cstauffer/archive/2008/06/13/client-health-check-script-and-scheduled-task-version-1-1-release.aspx

Thanks Chris Stauffer <><

 Finally Games for the Zune.

 Guides to install Games

http://www.zuneboards.com/forums/tutorials/23605-installing-game-xna-your-zune.html#post216424
 
http://www.zunescene.mobi/forums/index.php?topic=37524.0
 
http://www.zunescene.mobi/forums/index.php?topic=37503.0

 
Here is what I uploaded so far. As I find more I will add them to this blog post:

 
These guys are going crazy:

http://forums.xna.com/thread/60532.aspx

The first Zune Clock (Not a Game)

http://www.zuneboards.com/forums/download-completed-games/23700-ctp-offical-zuneboards-clock.html

GAMES:

Alien Aggressors
http://nick.gravelyn.com/2008/05/07/alien-aggressors-zune-edition/
(For the updated ZunePad version files, go here

Galactic Wars 3 (Zune - Source)

http://focusedgames.com/Content.aspx?id=175

Rock Rain:
http://www.sharpgames.net/Noticias/Rock+Rain+Zune.xna

XNA Tetris:
www.csc.calpoly.edu/~mwazny/tetris.zip

Collapse:
http://www.guyer.us/downloads/collapse.zip

A Bejeweled Stlye game:
http://focusedgames.com/downloads/MatchEm_050908.zip

 Fonts (Grab these  fast because every site that had them mysteriously disappeared)

http://www.4shared.com/file/46099068/9ef9bbfa/Segoe.html

http://go.microsoft.com/fwlink/?LinkId=104778&clcid=0x409

Also note that exiting most of the games causes the Zune to reboot including the Clock. 

Updated:

Major list of games: 

http://www.zuneboards.com/forums/download-completed-games-174/

Brief Description

MUI if you need it

Brief Description

http://www.microsoft.com/downloads/details.aspx?familyid=D3F8F6AB-84F1-4095-8709-DF509B1BEE22&displaylang=en

Here is the ISO if you need it

Brief Description

http://www.microsoft.com/downloads/details.aspx?familyid=2FCDE6CE-B5FB-4488-8C50-FE22559D164E&displaylang=en

You can now download XP SP3 though windows Update or here

Brief Description

http://www.microsoft.com/downloads/details.aspx?FamilyId=5B33B5A8-5E76-401F-BE08-1E1555D4F3D4&displaylang=en

Windows XP Service Pack 3 Overview

http://www.microsoft.com/downloads/details.aspx?FamilyID=68c48dad-bc34-40be-8d85-6bb4f56f5110&displaylang=en

 SCCM Central server can handle 200k client

SCCM Primary server connected to a central server can handle 100k cleints

 SHAPE  \* MERGEFORMAT

Installing Clients

Supported Client Platforms

• 2k sp4
• XP SP2
• Vista Buissness, Enterprise, Ultimate

Supported Server Client Platforms

• Server 2k SP4
• Server 2003 SP1,2 and R2
• Server 2008

Supported Mobile Client Platforms

• Win Mobile

Deployment Methods

• Client Push
• Logon installation for high rights
• No longer support for low rights- Must be an Admin
• Software Distribution
• Manual

New Methods

• GPO
• Install client as an MSI with CCMSetup.MSI
• 2 ADM Templates are provided

§         Located in Tools folder

• SUP
• Client distributed as a patch

Client Installation Process

All of the following will install automatically when the client is installed. You can stage it but there is no need. The CCMsetup.exe will asses the system and decide what is needed.

This is the sequence of installation for the client:

• CCMSetup.exe - bandwidth aware
• Bits 2.0- 3.0
• 2.0 - windows 2000 requires a reboot
• 2.5 - XP only needs a reboot if client is installed via the SUP
• 3.0 - is built into Vista
• Windows installer 3.1v2
• Windows Update Service
• Core XML 6.0 Sp1
• MSRDC- needed to create a branch DP but it installs during the client install so it is not needed later.
• WIMGAPI.MSI

To uninstall use CCMSetup.exe /Uninstall

• do not use CCMCLEAN.exe

Note:

• Client.MSI can not run Solo anymore. You must run CCMSetup.exe
• Site code is validated before installation so if it is wrong it will tell you
• If AD is not extended then you will need an SLP other wise it is not needed.
• Client Registration
• Mixed mode client uses a personal certificate
• Native mode the client uses the Server Certificate
• Client Must get approved
• 3 ways to get approval
• Manual
• Auto approval if on domain (Default)
• Auto Approve all systems that make request
• Do not change the FSP time window in production
• Install default is now SMSSITECODE=Local Site Code
• No longer Auto
• No longer uses remote registry
• No uses Remote WMI
• Client Push is published to AD
• When you put the command line into the Client Push section it is published to AD so you no longer need to have the command line every time you install a client. The CCMINSTALL.exe will check AD for the switches before it installs.
• To turn on Verbose logging for the client install in the DDM.LOG change the following key to Verbose Logging =1

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DISCOVERY_DATA_MANAGER]

"Verbose logging"=dword:00000001

SUP Installation

• Remove the GPO for WSUS
• Install WSUS 3.0 SP1 on your SCCM Server
• Install the SUP
• Publish to AD the location of the WSUS server
• This will allow you to install the clients via WSUS
• Once client is install it will change the WSUS entries in the policy to reflect the changes from the SUP.
• Note: if the client is installed VIA the SUP it will get rebooted because Windows update is doing the install so there is not way to stop the reboot.

• With the FSP you get 7 reports that will allow you to track client installation

• Config Mgr SP1 due in May
• Confg Mgr  R2 is due for RC in July
• MS Framework V 4 is released
• DOP Q3 2008 must have SA
• MDT Dell Server Deployment Pack coming this summer
• R2 will have multi cast
• Virtualization is the future
• VMM 2008 Beta is released
• Can manage VMware, MSVM, MSHVM
• Manage Linux though SCOM
• Cross Platform Extensions Beta released
• Open source clients coming

Just a quick update for anybody that read my first post from MMS. My father in-law is doing great and is now home. He had a Epidural hematoma from a logging accident that happened back in January and like most of us typical men figured it was just a head ache and shook it off until it was almost too late. Good thing that my mother in-law is an LPN and picked up what that something was wrong before it was to late.

 So he is home now with a big scare across his head and a titanium plate in his head. When he got home Mom gave him a  buzz cut because they only partially shaved his head since it was an emergency surgery. His only response was dang i haven't been cut this short since i was in the military 40 years ago.

Thanks for the prayers

 Chris and Sharon Stauffer <>< 

 
Quote: With great Power comes Great Responsibility (Uncle Ben to Spider-Man)

Console Switches

• SMS:Debugview
• SMS:verboseerrors
• SMS:NoRestore

Get Crimson Editor to edit XML for console extensions.

Go to Greg Ramsey’s blog to get XML guid locator

Watch Greg’s blog for the DP update Script. He said that it wil be able to update all DP’s with packages at once instead of having to use the built in tool that requires you to do the cloning on each node which is very annoying. So I wait with batted breath for the script J

There was a lot more covered in this presentation but most of it is on Greg’s blog so I wont repeat his work.

Top 10 Joke list was corny

SMS is presently used for:

• MS.com
• Xbox Live
• MS Surface

State messages are used for:

• Client deployment
• Patch Management
• DCM
• CAL Tracking

SQL can be moved off the box if you have a dedicated 1 GIG connection between boxes.

• On a personal note for this topic: I would not recommend this unless the server is in the same rack and you have a direct connection between the 2 boxes. I know in my network the trip from server to server would require the system to go out onto the WAN and make 2 trips though 2 firewalls just to transmit the data and even with 1 GIG connections this would end up bottlenecked somewhere.

Cool tool for presentations called Zoom it will allow you to zoom into a screen shot so that people can actually see what you are talking about in a presentation Demo.

Looking ahead

SP1

• Hot Fixes
• Integration with R2
• W2k8 Support
• Vista SP1 Support
• Feature addons
• AI 1.5 added
• This wil connect to the Live cloud for information, which means no more need for updates because you can get them live.
• Intel AMT Integration
• Out of band Remote Management

R2

• Application Virtualization
• Client Status Reporting
• New OSD Server Provisioning
• Multi Casting
• Forefront Integration
• New Client Health Tool

What else is coming?

 DCM Improvements and a tool to build them for you.

 Here is the first of may post on my notes from MMS. Hope this helps someone else who didnt attend or couldnt get to this session:

·        An SLP is only needed if you are not using the AD integration. But by  the sounds of it, it may be a good idea to have just incase you cant get to AD but you can still get to WINS. If you want it in WINS you will need to manually enter it.

·        You should place the FSP on a separate server. The whole point of having an FSP is so that the client can report to something if the event that it cant reach the MP.

o       It can be as simple as a VM server because it is just a message relay  point.

·        Then installing the SCCM client use the following command line to assign an FSP

o       FSP= Servername

·        Some other Commandline options

·        Instead of using SMSSite= auto

o       Use SMSSite=Local

Important Client notes to remember.

·        Windows 2000 machines will require a reboot to install the client if Bits 2.0 is not install previously.

·        You can use the Task Sequence from OSD to chain packages together for a more efficient deployment of software

 I was actually mentioned in Paul's SI21 Advances in SMS 2003 and Configuration Manager 2007 Client Health Management.

WOW what an honor to be mentioned in front of a croud of about 500+ people by a Sr SMS admin at Microsoft.

Not one but 2 times in the slides and i think at least 1 time by name in the actual presentation.