Enable DebugLogging and Verbose logging on sccm clients

I’m working with SCCM and needed to troubleshoot some client items with task sequences.


Enabling Debug and Verbose Logging


To enable debug logging after installation, create the following registry key:
HKLM\SOFTWARE\Microsoft\CCM\Logging\debuglogging


To enable verbose logging after installation, change the following value to 0.  You will need to right click on the @Global key and change permissions to allow the current user to change the data in the key.
HKLM\Software\Microsoft\CCM\Logging\@Global\Loglevel


64 bit boxes
—————-
HKLM\Software\Wow6432Node\Microsoft\CCM .


32 bit boxes
—————-
HKLM\Software\Microsoft\CCM


Reference links


Webfarm and IIS configuration tips/tricks

I was recently talking with some good friends about tips for performance and what an IIS Administrator could do on the server side.  I also see this question from time to time in the forums @ http://forums.iis.net.    Of course, you should test individual settings in a controlled environment while performing load testing before just implementing on your production farm. 



Additionally, some basic counters in for measuring applications is: I would recommend checking out the Chapter 17 in IIS 7 Resource kit. it was one of the chapters I authored. 🙂




  • Concurrent Connections, 


  • Request Per / Sec,


  • Request Queued. 

I strongly suggest testing one change at a time to see how it helps improve your performance.  Hopefully this post provides a few options to review in your environment.  


Cheers,


Steve Schofield
Windows Server MVP – IIS
http://weblogs.asp.net/steveschofield
 
http://www.IISLogs.com
Log archival solution
Install, Configure, Forget

Using SCCM to publish a powershell script via a Package / Program / Advertisement

I was recently trying to publish a powershell script via an SCCM Package / Program / Advertisement.  My ‘bingfu’ and ‘googlefu’ was not working.  I asked on the absolute best SCCM listserv run by http://myitforum.com (Rod Trent and company).  Todd Hemsell provided the link below which was doing EXACTLY what I wanted. 


http://www.patricktowles.com/2010/10/running-powershell-scripts-as.html


Of course, there is more to the story.   However, my script was not working.  I kept getting Error Code 1 in the execmgr.log on the client.   One of the things unique to my environment is all servers are x64.  SCCM client runs as 32 bit, which in turns run (x86) powershell, which resides below the c:\windows\sysWOW64 folder.   We have scripts required to be AllSigned and set in the Group Policy administrative template.  The GPO only sets the AllSigned on the 64 bit powershell I later found out.  I manually set the execution policy (Set-ExecutionPolicy) to All Signed.  Here is the registry entry to set.


HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell


You can set this setting via Preferences in Group Policy or manually set on the machine running Set-ExecutionPolicy within the (x86) powershell window to AllSigned  Thanks to Todd and the list for putting me on the right track.  Hopefully this helps someone else and what is %~dp0%1 (only syntax a programmer would love) :))))


Cheers,


Steve Schofield
Microsoft MVP – IIS