ConfigMgrDogs

  • ConfigMgr 2012 Automatic Deployment Rules

     

    In CM12 we have a number of changes in Software Updates. One of the most anticipated one’s is Auto Deployment Rules.

    Yes finally I hear you say….

    Well Lets run through creating an Auto Deployment and one little gotcha to keep your eye on.

    In the Console we select

     Software Library > Software Updates > Automatic Deployment Rules

    Choose Create Automatic Deployment Rule from the Ribbon or Right click on the mouse.

          image

     

    In the first screen we can choose a Template

    (Templates are no longer a node in the console they are now created when creating an Auto Deployment Rule or manually Deploying Updates and are saved at the Summary screen.Ill point this out later in the post)

    image

     

     

     

    You can Select to Add to an Existing Software Update Group or Create a new Software Update Group.

    image

    If you select Add to an Existing Software Update Group a brand new group will be created the first time the Auto Deployment Rule is run and every time the rule runs after that the new updates are added to that group.

    (NOTE You cannot create a software Update group manually and then create an Auto Deployment rule to add new updates to that group. Even if you give it the same name and description the Auto Deployment Rule will still create a new group. See Figure below.The group created at 6:02 pm was done manually. I then ran the Auto Deployment rule at 6:07 pm and you can see that it creates a group with a duplicate name and description.)

    image

     

    If you select Create a new Software Update Group every time the rule is run a new Software Update Group is created.

     

    You can also choose to Enable the deployment after the rule is run.

     

    Here you can choose to use Wake on lan and also decide whether to automatically deploy all updates and approve any license agreements or deploy only updates that do not include license agreements.

    image

    This is where you select the requirements to select the updates to auto approve.

     

    image

    Here you can set a Schedule for the Rule to run. Potentially every Patch Tuesday or Daily for Forefront updates.

    Or you can run the rule manually.

    image

    Similar to CM07 we can set the deployment schedule and whether the Deployment will be Mandatory.

    image

    Set the User Experience, deadline behaviour and reboot suppression.

    image

    We can now Generate Alerts if the compliance falls below a certain after a certain period of time. As before we can select to disable alerts for Operations Manager.

    image

    Set your Deployment options

    image

    Either select an existing package or create a new one for the new updates

    image

    Select a DP or DP Group

    image

    Where to download the updates from

    image

     

    Choose a language

    image

    On the Summary screen you can Choose to Save your settings as a Template for future use

    image

    image

    We now see the new Rule in the console and we can choose to Run Now from the ribbon.

    image

    image

    The log file for troubleshooting is Ruleengine.log

    We can see the Auto Deployment Rule is kicked off

    image

    Evaluating and downloading updates

    image

    Here we see it looking for an existing update group and not finding one therefore creating a new Software Update Group then adding the updates to that Group.

    image

    Back to the console.If we select Software Update Groups we now see the newly created Windows 7 Automatic Deployment and the Deployment (Yet to be enabled) on the tab below.

    image

    When we select Show Members we can see the updates applied.

    image

    and there you have it.

  • Windows 8 and Windows 8.1 New Group Policy Settings

    Windows 8 RTM

    For full details, download the following file

    image

     Policy Setting Name 
     
     Allow all trusted apps to install 
     Allow deployment operations in special profiles 
     Block launching desktop apps associated with a file. 
     Block launching desktop apps associated with a protocol 
     Block launching desktop apps associated with a file. 
     Block launching desktop apps associated with a protocol 
     Do not display the lock screen 
     Prevent changing lock screen image 
     Prevent changing start menu background 
     Turn on PIN sign-in 
     Turn off picture password sign-in 
     Do not display the password reveal button 
     Do not display the password reveal button 
     Device compatibility settings 
     Driver compatibility settings 
     Specify the search server for device driver updates 
     Turn off smart multi-homed name resolution 
     Turn off smart protocol reordering 
     Allow NetBT queries for fully qualified domain names 
     Prefer link local responses over DNS when received over a network with higher precedence 
     Turn off IDN encoding 
     IDN mapping 
     Use solid color for Start background 
     Turn on misconversion logging for misconversion report 
     Turn off saving auto-tuning data to file 
     Turn off history-based predictive input 
     Turn off Open Extended Dictionary 
     Turn off Internet search integration 
     Turn off custom dictionary 
     Restrict character code range of conversion 
     Do not include Non-Publishing Standard Glyph in the candidate list 
     Boot-Start Driver Initialization Policy 
     Turn off switching between recent apps 
     Turn off tracking of app usage 
     Do not allow Windows to activate Enhanced Storage devices 
     Do not throttle additional data 
     Send additional data when on battery power 
     Send data when on connected to a restricted/costed network 
     Do not throttle additional data 
     Send additional data when on battery power 
     Send data when on connected to a restricted/costed network 
     Windows To Go Default Startup Options 
     Allow hibernate (S4) when starting from a Windows To Go workspace 
     Disallow standby sleep states (S1-S3) when starting from a Windows to Go workspace 
     Turn off File History 
     Configure maximum age of file server shadow copies 
     Allow or Disallow use of encryption to protect the RPC protocol messages between File Share Shadow Copy Provider running on application server and File Share Shadow Copy Agent running on the file servers. 
     Enable / disable TXF deprecated features 
     Enable optimized move of contents in Offline Files cache on Folder Redirection server path change 
     Redirect folders on primary computers only 
     Redirect folders on primary computers only 
     Turn off offer text predictions as I type 
     Turn off insert a space after selecting a text prediction 
     Turn off autocorrect misspelled words 
     Turn off highlight misspelled words 
     Disallow copying of user input methods to the system account for sign-in 
     Block clean-up of unused language packs 
     Enable AD/DFS domain controller synchronization during policy refresh 
     Turn off Group Policy Client Service AOAC optimization 
     Configure Direct Access connections as a fast network connection 
     Change Group Policy processing to run asynchronously when a slow network connection is detected. 
     Configure Group Policy slow link detection 
     Specify workplace connectivity wait time for policy processing 
     Enable Hotspot Authentication 
     Turn off access to the Store 
     Turn off access to the Store 
     Turn off flip ahead feature 
     Turn on Enhanced Protected Mode 
     Do not allow ActiveX controls to run in Protected Mode when Enhanced Protected Mode is enabled 
     Always send Do Not Track header 
     Turn off encryption support 
     Show Content Advisor on Internet Options 
     Go to an intranet site for a one-word entry in the Address bar 
     Install binaries signed by MD2 and MD4 signing technologies 
     Prevent managing SmartScreen Filter 
     Prevent bypassing SmartScreen Filter warnings about files that are not commonly downloaded from the Internet 
     Turn off browser geolocation 
     Turn off Adobe Flash in Internet Explorer and prevent applications from using Internet Explorer technology to instantiate Flash objects 
     Automatically activate newly installed add-ons 
     Turn off add-on performance notifications 
     Turn on ActiveX Filtering 
     Prevent deleting download history 
     Prevent deleting ActiveX Filtering and Tracking Protection data 
     Allow Internet Explorer 8 shutdown behavior 
     Specify default behavior for a new tab 
     Notify users if Internet Explorer is not the default web browser 
     Turn off URL Suggestions 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Allow Internet Explorer to play media files that use alternative codecs 
     Prevent configuration of top-result search on Address bar 
     Do not display the reveal password button 
     Turn off the WebSocket Object 
     Set the maximum number of WebSocket connections per server 
     Display tabs on a separate row 
     Establish InPrivate Filtering threshold 
     Establish Tracking Protection threshold 
     Turn off Tracking Protection 
     Use Policy List of Quirks Mode sites 
     Turn off ability to pin sites in Internet Explorer on the desktop 
     Set default storage limits for websites 
     Allow websites to store indexed databases on client computers 
     Set indexed database storage limits for individual domains 
     Set maximum indexed database storage limit for all domains 
     Allow websites to store application caches on client computers 
     Set application cache storage limits for individual domains 
     Set maximum application caches storage limit for all domains 
     Set application caches expiration time limit for individual domains 
     Set maximum application cache resource list size 
     Set maximum application cache individual resource size 
     Start Internet Explorer with tabs from last browsing session 
     Open Internet Explorer tiles on the desktop 
     Set how links are opened in Internet Explorer 
     Turn off flip ahead feature 
     Turn on Enhanced Protected Mode 
     Do not allow ActiveX controls to run in Protected Mode when Enhanced Protected Mode is enabled 
     Always send Do Not Track header 
     Show Content Advisor on Internet Options 
     Go to an intranet site for a one-word entry in the Address bar 
     Install binaries signed by MD2 and MD4 signing technologies 
     Prevent managing SmartScreen Filter 
     Prevent bypassing SmartScreen Filter warnings about files that are not commonly downloaded from the Internet 
     Disable Import/Export Settings wizard 
     Turn off browser geolocation 
     Turn off Adobe Flash in Internet Explorer and prevent applications from using Internet Explorer technology to instantiate Flash objects 
     Automatically activate newly installed add-ons 
     Turn off add-on performance notifications 
     Turn on ActiveX Filtering 
     Prevent deleting download history 
     Prevent deleting ActiveX Filtering and Tracking Protection data 
     Allow Internet Explorer 8 shutdown behavior 
     Specify default behavior for a new tab 
     Disable changing secondary home page settings 
     Turn off URL Suggestions 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Render legacy filters 
     Enable dragging of content from different domains within a window 
     Enable dragging of content from different domains across windows 
     Turn off Print Menu 
     Allow Internet Explorer to play media files that use alternative codecs 
     Prevent configuration of search on Address bar 
     Prevent configuration of top-result search on Address bar 
     Do not display the reveal password button 
     Turn off the WebSocket Object 
     Set the maximum number of WebSocket connections per server 
     Display tabs on a separate row 
     Turn on Suggested Sites 
     Establish InPrivate Filtering threshold 
     Establish Tracking Protection threshold 
     Turn off Tracking Protection 
     Use Policy List of Quirks Mode sites 
     Turn off ability to pin sites in Internet Explorer on the desktop 
     Set default storage limits for websites 
     Allow websites to store indexed databases on client computers 
     Set indexed database storage limits for individual domains 
     Set maximum indexed database storage limit for all domains 
     Allow websites to store application caches on client computers 
     Set application cache storage limits for individual domains 
     Set maximum application caches storage limit for all domains 
     Set application caches expiration time limit for individual domains 
     Set maximum application cache resource list size 
     Set maximum application cache individual resource size 
     Start Internet Explorer with tabs from last browsing session 
     Open Internet Explorer tiles on the desktop 
     Set how links are opened in Internet Explorer 
     Install new versions of Internet Explorer automatically 
     KDC support for claims, compound authentication and Kerberos armoring 
     Warning for large Kerberos tickets 
     Specify KDC proxy servers for Kerberos clients 
     Disable revocation checking for the SSL certificate of KDC proxy servers 
     Fail authentication requests when Kerberos armoring is not available 
     Support compound authentication 
     Set maximum Kerberos SSPI context token buffer size 
     Kerberos client support for claims, compound authentication and Kerberos armoring 
     Hash Version support for BranchCache 
     Turn off Windows Location Provider 
     Show first sign-in animation 
     Do not enumerate connected users on domain-joined computers 
     Enumerate local users on domain-joined computers 
     Turn off app notifications on the lock screen 
     Automatic Maintenance Activation Boundary 
     Automatic Maintenance Random Delay 
     Automatic Maintenance WakeUp Policy 
     Turn off shared components 
     Prevent embedded UI 
     Support Email Address 
     Friendly Name 
     User Interface 
     Prefer Local Names Allowed 
     DirectAccess Passive Mode 
     Corporate Resources 
     IPsec Tunnel Endpoints 
     Custom Commands 
     Specify passive polling 
     Do not use NetBIOS-based discovery for domain controller location when DNS-based discovery fails 
     Specify address lookup behavior for DC locator ping 
     Use urgent mode when pinging domain controllers 
     Internet proxy servers for apps 
     Intranet proxy servers for  apps 
     Private network ranges for  apps 
     Proxy definitions are authoritative 
     Subnet definitions are authoritative 
     Remove "Work offline" command 
     Remove "Work offline" command 
     Enable file synchronization on costed networks 
     Detect compatibility issues for applications and drivers 
     Enable Automatic Hosted Cache Discovery by Service Connection Point 
     Configure Client BranchCache Version Support 
     Configure Hosted Cache Servers 
     Set age for segments in the data cache 
     Turn on Module Logging 
     Set the default source path for Update-Help 
     Turn on Module Logging 
     Set the default source path for Update-Help 
     Isolate print drivers from applications 
     Always rasterize content to be printed using a software rasterizer 
     Do not allow v4 printer drivers to show printer extensions 
     Change Microsoft XPS Document Writer (MXDW) default output format to the legacy Microsoft XPS format (*.xps) 
     Turn off storage and display of search history 
     Always use automatic language detection when indexing content and properties 
     Do not sync 
     Do not sync app settings 
     Do not sync passwords 
     Do not sync personalize 
     Do not sync other Windows settings 
     Do not sync desktop personalization 
     Do not sync browser settings 
     Do not sync on metered connections 
     File Classification Infrastructure: Display Classification tab in File Explorer 
     File Classification Infrastructure: Specify classification properties list 
     Enable access-denied assistance on client for all file types 
     Clear history of tile notifications on exit 
     Prevent users from uninstalling applications from Start 
     Show "Run as different user" command on Start 
     Do not allow taskbars on more than one display 
     Set IP Stateless Autoconfiguration Limits State 
     Specify default connection URL 
     Limit maximum display resolution 
     Suspend user sign-in to complete app registration 
     Configure image quality for RemoteFX Adaptive Graphics 
     Configure RemoteFX Adaptive Graphics 
     Allow RDP redirection of other supported RemoteFX USB devices from this computer 
     Configure RemoteFX 
     Optimize visual experience when using RemoteFX 
     Enable RemoteFX encoding for RemoteFX clients designed for Windows Server 2008 R2 SP1 
     Select network detection on the server 
     Select RDP transport protocols 
     Turn Off UDP On Client 
     Turn off Fair Share CPU Scheduling 
     Use the hardware default graphics adapter for all Remote Desktop Services sessions 
     Configure image quality for RemoteFX Adaptive Graphics 
     Configure RemoteFX Adaptive Graphics 
     Enable Remote Desktop Protocol 8.0 
     Select network detection on the server 
     Select RDP transport protocols 
     Turn Off UDP On Client 
     Turn on TPM backup to Active Directory Domain Services 
     Configure the level of TPM owner authorization information available to the operating system 
     Standard User Lockout Duration 
     Standard User Individual Lockout Threshold 
     Standard User Total Lockout Threshold 
     User management of sharing user name, account picture, and domain information with apps (not desktop apps) 
     Download roaming profiles on primary computers only 
     Set user home folder 
     Choose drive encryption method and cipher strength 
     Configure use of passwords for operating system drives 
     Reset platform validation data after BitLocker recovery 
     Disallow standard users from changing the PIN or password 
     Use enhanced Boot Configuration Data validation profile 
     Enforce drive encryption type on operating system drives 
     Allow network unlock at startup 
     Enable use of BitLocker authentication requiring preboot keyboard input on slates 
     Allow Secure Boot for integrity validation 
     Enforce drive encryption type on fixed data drives 
     Enforce drive encryption type on removable data drives 
     Prohibit connection to non-domain networks when connected to domain authenticated network 
     Minimize the number of simultaneous connections to the Internet or a Windows Domain 
     Prohibit connection to roaming Mobile Broadband networks 
     Disable power management in connected standby mode 
     Location where all default Library definition files for users/machines reside. 
     Start File Explorer with ribbon minimized 
     Location where all default Library definition files for users/machines reside. 
     Configure Windows SmartScreen 
     Show lock in the user tile menu 
     Show sleep in the power options menu 
     Show hibernate in the power options menu 
     Do not show the 'new application installed' notification 
     Start File Explorer with ribbon minimized 
     Set a default associations configuration file 
     Allow the use of remote paths in file shortcut icons 
     Disallow WinRM from storing RunAs credentials 
     Require use of fast startup 
     Turn off the Store application 
     Turn off the Store application 
     Allow Store to install apps on Windows To Go workspaces 
     Turn off Automatic Download of updates 
     Set Cost 
     Turn off tile notifications 
     Turn off toast notifications 
     Turn off toast notifications on the lock screen 
     Turn off notifications network usage 
     Set 3G Cost 
     Set 4G Cost 

    Windows 8.1

    For full details, download the following file

    image

     Policy Setting Name 
     
     Allow development of Windows Store apps without installing a developer license 
     Prevent enabling lock screen slide show 
     Prevent enabling lock screen camera 
     Force a specific background and accent color 
     Force a specific Start background 
     Force a specific default lock screen image 
     Allow users to select when a password is required when resuming from connected standby 
     Restrict delegation of credentials to remote servers 
     Prevent adding
     App switching 
     Charms 
     WinX 
     Automatically send memory dumps for OS-generated error reports 
     Automatically send memory dumps for OS-generated error reports 
     Configure Group Policy Caching 
     Configure Logon Script Delay 
     Turn off loading websites and content in the background to optimize performance 
     Turn on the swiping motion on Internet Explorer for the desktop 
     Turn on 64-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows 
     Allow Internet Explorer to use the SPDY/3 network protocol 
     Turn off phone number detection 
     Allow Microsoft services to provide enhanced suggestions as the user types in the Address bar 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Turn off loading websites and content in the background to optimize performance 
     Turn on the swiping motion on Internet Explorer for the desktop 
     Turn on 64-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows 
     Allow Internet Explorer to use the SPDY/3 network protocol 
     Turn off phone number detection 
     Allow Microsoft services to provide enhanced suggestions as the user types in the Address bar 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Don't run antimalware programs against ActiveX controls 
     Prevent deleting ActiveX Filtering
     Prevent deleting ActiveX Filtering
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     Allow cut
     KDC support for claims
     Kerberos client support for claims
     Automatic Maintenance Random Delay 
     Use DNS name resolution when a single-label domain name is used
     At logoff
     Run Windows PowerShell scripts first at computer startup
     Run Windows PowerShell scripts first at user logon
     Run Windows PowerShell scripts first at user logon
     Disable indexing of removable drives 
     Don't search the web or display web results in Search 
     Don't search the web or display web results in Search over metered connections 
     Set what information is shared in Search 
     Set the SafeSearch setting for Search 
     Do not sync Apps 
     Do not sync start settings 
     
     
     
     Pin Apps to Start when installed 
     Start Screen Layout 
     Default 
     Default app 
     Default search 
     Sort 
     Multimon 
     Pin Apps to Start when installed 
     Start Screen Layout 
     Remove and prevent access to the Shut Down
     For tablet pen input
     For tablet pen input
     For touch input
     For touch input
     Include rarely used Chinese
     Include rarely used Chinese
     Set remote control session UAC desktop 
     Use advanced RemoteFX graphics for RemoteApp 
     Set remote control session UAC desktop 
     Set remote control permission request timeout 
     Enable Remote Desktop Protocol 8.0 
     User management of sharing user name
     Choose drive encryption method and cipher strength (Windows Vista
     Configure TPM platform validation profile (Windows Vista
     Allow antimalware service to startup with normal priority 
     Turn on virus definitions 
     Configure local administrator merge behavior for lists 
     Define addresses to bypass proxy server 
     Define proxy server for connecting to the network 
     Randomize scheduled task times 
     Allow antimalware service to remain running always 
     Extension Exclusions 
     Path Exclusions 
     Process Exclusions 
     Turn on protocol recognition 
     Turn on definition retirement 
     Define the rate of detection events for logging 
     IP address range Exclusions 
     Port number  Exclusions 
     Process Exclusions for outbound traffic 
     Threat ID Exclusions 
     Specify additional definition sets for network traffic inspection 
     Configure local setting override for the removal of items from Quarantine folder 
     Configure removal of items from Quarantine folder 
     Turn on behavior monitoring 
     Turn on Information Protection Control 
     Turn on network protection against exploits of known vulnerabilities 
     Scan all downloaded files and attachments 
     Monitor file and program activity on your computer 
     Turn on raw volume write notifications 
     Turn on process scanning whenever real-time protection is enabled 
     Define the maximum size of downloaded files and attachments to be scanned 
     Configure local setting override for turn on behavior monitoring 
     Configure local setting override for monitoring file and program activity on your computer 
     Configure local setting override to turn off Intrusion Prevention System 
     Configure local setting override for scanning all downloaded files and attachments 
     Configure local setting override to turn on real-time protection 
     Configure local setting override for monitoring for incoming and outgoing file activity 
     Configure monitoring for incoming and outgoing file and program activity 
     Configure local setting override for the time of day to run a scheduled full scan to complete remediation 
     Specify the day of the week to run a scheduled full scan to complete remediation 
     Specify the time of day to run a scheduled full scan to complete remediation 
     Configure time out for detections requiring additional action 
     Configure time out for detections in critically failed state 
     Configure Watson events 
     Configure time out for detections in non-critical failed state 
     Configure time out for detections in recently remediated state 
     Configure Windows software trace preprocessor components 
     Configure WPP tracing level 
     Allow users to pause scan 
     Specify the maximum depth to scan archive files 
     Specify the maximum size of archive files to be scanned 
     Specify the maximum percentage of CPU utilization during a scan 
     Scan archive files 
     Turn on catch-up full scan 
     Turn on catch-up quick scan 
     Turn on e-mail scanning 
     Turn on heuristics 
     Scan packed executables 
     Scan removable drives 
     Turn on reparse point scanning 
     Create a system restore point 
     Run full scan on mapped network drives 
     Scan network files 
     Configure local setting override for maximum percentage of CPU utilization 
     Configure local setting override for the scan type to use for a scheduled scan 
     Configure local setting override for schedule scan day 
     Configure local setting override for scheduled quick scan time 
     Configure local setting override for scheduled scan time 
     Turn on removal of items from scan history folder 
     Specify the interval to run quick scans per day 
     Start the scheduled scan only when computer is on but not in use 
     Specify the scan type to use for a scheduled scan 
     Specify the day of the week to run a scheduled scan 
     Specify the time for a daily quick scan 
     Specify the time of day to run a scheduled scan 
     Define the number of days before spyware definitions are considered out of date 
     Define the number of days before virus definitions are considered out of date 
     Define file shares for downloading definition updates 
     Turn on scan after signature update 
     Allow definition updates when running on battery power 
     Initiate definition update on startup 
     Define the order of sources for downloading definition updates 
     Allow definition updates from Microsoft Update 
     Allow real-time definition updates based on reports to Microsoft MAPS 
     Specify the day of the week to check for definition updates 
     Specify the time to check for definition updates 
     Allow notifications to disable definitions based reports to Microsoft MAPS 
     Define the number of days after which a catch-up definition update is required 
     Specify the interval to check for definition updates 
     Check for the latest virus and spyware definitions on startup 
     Configure local setting override for reporting to Microsoft MAPS 
     Specify threats upon which default action should not be taken when detected 
     Specify threat alert levels at which default action should not be taken when detected 
     Display notifications to clients when they need to perform actions 
     Display additional text to clients when they need to perform an action 
     Always automatically restart at the scheduled time 
     Specify Work Folders settings 
     Turn off tile notifications 
     Turn off toast notifications 
     Turn off toast notifications on the lock screen 
     Turn off notifications network usage 
     Turn off Quiet Hours 
     Set the time Quiet Hours begins each day 
     Set the time Quiet Hours ends each day 
     Turn off calls during Quiet Hours 
     Set 3G Cost 
     Set 4G Cost 
  • Set Windows 8 Lock Screen Image (KB2770917)

    Microsoft have recently released a Windows 8 and Server 2012 cumulative update KB2770917.

    http://support.microsoft.com/kb/2770917

    One of the important features of this update is the ability to customize the Windows 8 lock screen with corporate branding and set this across your domain joined computers using Group Policy.

    From the KB:

    This cumulative update includes the following performance and reliability improvements:

    • Enable enterprise customers to customize the default lock screen.
    • Improves the performance when you wake the computer and when the computer is asleep, in order to improve battery life
    • Resolves an issue that may prevent Windows Store Apps from being installed fully
    • Other software updates and performance improvements

    After installing the update, you get four new Group Policy settings

    image

    Force a specific default lock screen image
    Provide a UNC or local path to your corporate lock screen logo, and all of your users will receive that as their lock screen.

    image

    Prevent changing lock screen image
    After setting the corporate lock image, enable this option if you don’t want your users to have the ability to personalize the lock screen image.

    image

     

    Prevent changing start menu background
    Use this option to stop your users from changing the Start Menu background colour. This means whatever the colour of the Start Menu background was when the machine was deployed will not be changed.

    image

     

    Do not display the lock screen
    Enabling this setting will remove the lock screen for any user who isn’t required to press CTRL+ALT+DEL to login.

     


     

    After configuring all the settings and applying the GPO, my corporate machines lock screen now looks like this, and my users are stuck with it!

     

    image

     

    Matt Shadbolt

  • Applying Windows Updates to a base WIM using DISM and Powershell

    Manual installation

    Firstly, locate your most up to date image and make a copy of it. This is so we can
    stream the newest Windows Updates into the mounted WIM without risk of damaging
    a working WIM. I suggest copying the WIM to a temp location. Also, put the
    Windows Update that you want to apply into an Updates folder.

    Next, mount your image in the temp location.

    DISM /Mount-Wim /WimFile:C:\TempMount\install.wim /index:1 /Mountdir:C:\TempMount\Mount

    Now inject the Windows Update you need to apply

    DISM /image:C:\TempMount\Mount /Add-Package /Packagepath:C:\Updates\

    Finally, save an unmount the image

    DISM /Unmount-Wim /Mountdir:C:\TempMount\Mount /commit
    DISM /Cleanup-Wim

    Automating the installation

    While running updates manually like this is an easy way to apply a few updates, hundreds of updates require more work. Here’s how you would apply the updates using PowerShell.

    $UpdatesPath = "C:\Updates\*"
    $MountPath = “C:\TempMount\Mount”
    $WimFile = “C:\TempMount\install.wim”
    DISM \Mount-Wim /WimFile:$WimFile /index:1 /Mountdir:$MountPath
    $UpdateArray = Get-Item $UpdatesPath
    ForEach ($Updates in $UpdateArray)
    {
    DISM /image:$MountPath /Add-Package /Packagepath:$Updates
    Start-Sleep –s 10
    }
    Write-Host "Updates Applied to WIM"
    DISM /Unmount-Wim /Mountdir:$MountPath /commit
    DISM /Cleanup-Wim

    Using SCCM 2007 Deployment Packages makes getting these updates really simple. Package up the updates like you would normally, then set the $UpdatesPath variable above to the SMS package location.

    Happy patching!

    Matt Shadbolt

  • Version and Build numbers for ConfigMgr 2012 RTM and SP1

    If you need to distinguish whether or not a site has been upgraded to ConfigMgr 2012 SP1, here is the process and version numbers.

     

    1. Open the ConfigMgr console

    2. Browse to Administration > Site Configuration > Sites

    3. Right-click on the site you need information for, and select Properties

    4. You’ll find the site version and build number here

    ConfigMgr 2012 RTM

    Version:  5.00.7711.0000
    Build number: 7711

    image

     

    ConfigMgr 2012 SP1

    Version:  5.00.7804.1000
    Build number:  7804

    clip_image002

    Matt Shadbolt

  • MDT Monitoring: Another Reason to Implement MDT 2012 Update 1 into your ConfigMgr 2012 SP1 Environment

    I have been doing a number of customer engagements recently around Windows 8 deployments through ConfigMgr 2012 SP1 and one question I often ask our customers during the planning phase is “Will you be integrating MDT 2012 Update 1 into your ConfigMgr 2012 SP1 environment?” The general response I get is “What are the benefits…?” Well the short answer is A LOT!!, but one of the cool new reasons is MDT 2012 Monitoring and the ability to use this to monitor your ConfigMgr 2012 SP1 OSD deployments.

    There are a few pre-requisites that are required to get the FULL functionality of what is offered in MDT 2012 monitoring in particular the option to DaRT Remote Control to your client machine during the build, even while in PXE. This will require a custom boot image to be created that includes the DaRT 8 utility embedded. As DaRT is part of the Microsoft Desktop Optimization Pack (MDOP) you will need an MDOP subscription.

    However if you do not have MDOP subscription you can still utilise the MDT 2012 Monitoring feature for your ConfigMgr 2012 SP1 deployments.

    In this session I will step through both configuring MDT 2012 Update 1 Monitoring for ConfigMgr 2012 SP1 OSD deployments as well as how to create a DaRT 8 embedded boot image to get the full power of MDT 2012 Monitoring.

    Section 1 – Configuring MDT 2012 Update 1 Monitoring

    Step 1: Install MDT 2012 Update 1 & Integrate it into your ConfigMgr 2012 SP1 Site

    clip_image002

    Step 2: Configure a MDT 2012 Update 1 Deployment Share

    - Open the MDT management MMC

    - Right Click Deployment Share \ New Deployment Share

    clip_image004

    - Complete the Wizard

    clip_image006

    clip_image008

    Step 5: Enable MDT Monitoring

    - Right Click your Deployment Share and select Properties

    - Select the Monitoring Tab

    - Enable Monitoring for this Deployment Share

    clip_image010

    Step 6: Modify your CustomSettings.ini file to use MDT Monitoring

    - Navigate to your source directory that your set for your MDT Settings Package

    - If you are not sure where it is check your ConfigMgr Package

    clip_image011

    - Open your CustomSettings.ini file using notepad

    - Add the following text to the end of the file: EventService=http://<server>:9800

    clip_image013

    - Update your Distribution Point to ensure the Settings Package is updated.

    NOTE: If you want to confirm your DP has been updated you can follow the steps outlined in one of my previous blogs – ConfigMgr 2012 Content Library Overview

    Step 7 – Deploy your MDT Client OSD Task Sequence

    clip_image015

    Step 8: Monitor your ConfigMgr 2012 SP1 OSD deployment through MDT 2012 Monitoring.

    - Open the MDT 2012 Update 1 Management Console

    - Expand your MDT Deployment Share

    - Select the Monitoring Node

    - Select the build you want to monitor and select Properties

    Note: You will not see your deployment appear until after the first “GATHER” has run during the Task Sequence.

    clip_image017

    clip_image019

    That’s all that needs to be done to start monitoring your ConfigMgr 2012 SP1 OSD Deployments using MDT 2012 Update 1 Monitoring.

    In the next section I will show you how to take monitoring further by using DaRT 8…

    Section 2 – Creating a DaRT8 Embedded Boot Image

    You will need to have integrated MDT 2012 Update 1 with your ConfigMgr 2012 SP1 environment and have a MDT 2012 Deployment Share configured before proceeding.

    Note: After Integrating MDT 2012 Update 1 with your ConfigMgr 2012 SP1 environment you will have the option to create a new MDT Boot Image directly out of the ConfigMgr UI Management console. However you will not have the option to select DaRT 8. The following steps will be required to make this option available.

    clip_image021

    The image above is what options you have out of the box when creating a custom MDT Boot Image in ConfigMgr 2012 SP1.

    NOTE that DaRT 8 is not an available option.. YET!!

    Step 1: Install DaRT 8 on your Server

    clip_image023

    This is only available for DaRT 8

    clip_image025

    - Complete the DaRT 8 Installation wizard

    Step 2: Prepare MDT 2012 Update 1 for DaRT 8

    - Using File Explorer, navigate to the C:\Program Files\Microsoft DaRT 8\v8 folder.

    - Copy the Toolsx86.cab file to C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86

    - Copy the Toolsx64.cab file to C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64

    clip_image027

    Step 3: Create a New ConfigMgr 2012 MDT Boot Image

    - Open the ConfigMgr 2012 Management Console

    - Select Software Library \ Operating Systems \ Boot Images

    - Right Click Boot Images and select “New MDT Boot Image”

    clip_image029

    - Complete the wizard

    - You will now notice we have a DaRT 8 option..

    clip_image031

    clip_image033

    Step 5: Configure your MDT Client Task Sequence to use your DaRT Boot Image

    clip_image034

    Step 7: Deploy your MDT Client Task Sequence using your DaRT 8 Boot Image

    clip_image036

    Step 8: Open MDT Monitoring and connect to your machine using DaRT Remote Connect

    - As we have deployed with a DaRT 8 embedded Boot Image we now have the option to connect to your client machine using DaRT Remote Control

    clip_image038

    You can now view your deployment status for any machine from start to finish even while it is in WinPE..

    clip_image040

    I hope you have found this information useful and will consider the benefits of integrating MDT 2012 Update 1 into your ConfigMgr 2012 SP1 environment, even if it is just for the monitoring components.

    Until next time…

  • ConfigMgr 2012 Incremental Collection Update/Delta Discovery

    Dynamic Collection Updates and Delta Discovery were features introduced in SCCM 2007 R3 and promised a lot. Finally, admins thought they could limit their full Collection updates to 1 per day, their AD System Group Discovery to 1 per day and use the Dynamic Updates/Delta Discovery to run every 5 minutes to pick up changes. Problem is, Dynamic Collection Updates/Delta Discovery do not work as we had hoped. In the end, Dynamic Collection Updates only worked on *newly* discovered systems… whether that’s a first time AD System Discover, OSD or manual client install. And hey, that’s great if your doing OSD!

    If you want your Advertisements to be available as soon as a machine has been built, then Dynamic Collection Updates are for you. But for alleviating the need to run your collection schedules every 15 minutes (against MS Best Practice) for software distribution, Dynamic Updates didn’t hit the mark.

    I’m happy to say that ConfigMgr 2012 now does Dynamic Updates and Delta Discovery in the way we had all hoped!

    And here’s the proof.

    Firstly, lets look at enabling CM12 Delta Discovery, creating a new group, adding a computer to the group and letting ConfigMgr 2012 do its thing:

    CM12 AD Group Discovery Settings

    1

    SCCM 2007 AD System Group Discovery Settings

    2

    Before Delta Discovery is run:

    SELECT * FROM v_R_System_SystemGroupName

    3

    From the Computer Object in SCCM

    4

    After Delta Discovery is run:

    SELECT * FROM v_R_System_SystemGroupName

    5

    From the Computer Object in SCCM

    6

    And for final proof – the adsgdis.log

    7

    So that’s great news! The Delta Discovery now works with System Group membership!

    One last thing we need to check – whether or not the Dynamic Collection Membership now picks up changes to existing machines… not just new objects created by DDRs.
    To check this, we’re going to create a Collection with a membership query looking for an AD group. If all goes well, within MAX 10 minutes, the computer should become a member of the new Collection.

    8

    9

    This time, we’re going to watch two logs – adsgdis.log and colleval.log and we should see the updates pretty soon.

    Adsgdis.log
    10

    Colleval.log
    11

    And now, within about 6 minutes we can see the Collection is now populated with the object!

    12

    Matt Shadbolt

  • Package Conversion Manager (PCM) in ConfigMgr 2012

    The ConfigMgr 2012 Package Conversion Manager (PCM) tool allows administrators to convert their legacy SCCM 2007 packages and programs into the new ConfigMgr 2012 Application and Deployment Types. This applies for all legacy packages apart from virtual APP-V packages that will automatically be converted to the new application model during the migration process. Once your legacy packages have been migrated and you have installed the Package Conversion Manager utility, then it is just a matter of analysing your packages in order to determine which readiness state it is in, and then converting your packages.

    There are still a number of bugs in the RTM version of the PCM tool but all in all it works well.

    It is worth noting that any legacy packages that have been configured to run another program first will only create the CM2012 Application Dependency if the program is in a different source Package ID. IE. “ Package with program dependent upon another program in the SAME package will not have that dependency converted” (from TechNet). To get around this you can just manually create the dependencies once you have converted your packages to Applications.

       

    Package Conversion Manager in Action..

    For this demonstration I am using an Adobe Reader X Package/Program with Package ID CEN0001A

    image

    1. Analyse your Package to Determine the Readiness State

    We need to Analyse a package to determine whether our package is in an appropriate state to be migrated to the new Application model or whether some remediation work will be required to prepare the package to be converted to an Application and more importantly into a Deployment Type.

    Expect to see either results after you have analysed your legacy package:

    1. Automatic – Your package is in a state that will allow for a successful migration to an Application

    2. Manual – Some remediation work on your legacy package is required before it can be successfully migrated to an Application Deployment Type.

     

    image

    Once the analysis is done you will see the readiness state under the Summary tab of your Package

    image

    If your legacy package returns an Automatic readiness state, than you can simply select the Convert Package option (This option will be GREYED out if Automatic is not returned) to convert your package to an Application.

    If your legacy package returns a Manual readiness state, than some work needs to be done to fix some issues before you can convert it to a CM 2012 Application.

    image

    2. Fix any Issues and Convert

    So we can see that my Adobe Reader package is not quite ready to be converted to a CM 2012 Application due to the Readiness state indicating Manual and the issue provided is because no Detection Method has been defined.

    NOTE: Application Detection Methods are mandatory for any CM 2012 Application so expect this as a common issue.

    So how do we fix this issue so my Adobe Reader package can be converted to a Application??? We use the Fix & Convert Tool to add the required information.

    image

     

    Wizard Screen Shots…

    image

    image

    image

     

    image

    image

     

    image

    image

    THATS IT, WE’RE DONE!!

    So if we now have a look under Applications we will see that we have an Adobe Reader X Application with a Deployment Type created for us.

    image

    AS SIMPLE AS THAT… GOOD LUCK!!

  • How NOIDMIFs can extend your Hardware Inventory

    ConfigMgr hardware inventory is a very important and widely used feature. We use it to collect all sorts of information, from hardware info such as disk configuration, amount of RAM, etc. Hardware Inventory is also used to query the Add/Remove Programs to see what software is installed on a machine.

    All hardware being queried by default can be found in your SMS_Def.mof file (%ConfigMgrInstallDir%\Inboxes\clifiles.src\hinv). There are heaps of WMI classes that are enabled by default – and even more than you manually need to enable. But sometimes we need to collect hardware information for a non-standard piece of hardware, or a device that isn’t included in the SMS_DEF.mof file.

    To cater for this type of inventory, we provide a function to extend the classes using special files call IDMIFS and NOIDMIFS.

    Creating custom Hardware Inventory classes

    By default the IDMIF/NOIDMIFS collection is not enabled, but to enable it open your Hardware Inventory Client Agent and tick the MIF collection boxes.

    image

    There's an interesting warning here – Enabling these settings increases your security risk by permitting ConfigMgr to collect and process unvalidated client data.

    IDMIFS/NOIDMIFS are unlike the SMS_DEF.mof file as they are unvalidated. This means they aren’t checked against any standard and can contain pretty much anything. The problem with this is, any user who is a local administrator on their machine, can add a NOIDMIF file to their CCM directory, and ConfigMgr will process this directly into the database and create custom tables. While this isn’t a huge problem, it would not be hard for a rouge user to create hundreds or thousands of extra tables in your ConfigMgr database.

    In my demo, I’m going to create a custom Hardware Inventory class called Wide World Asset Numbers. A company could use this class as a way to track asset numbers of their clients.

    First of all, from one of my clients I’m going to browse to %Windir%\System32\CCM\Inventory\Noidmifs

    To create this class, we create a text file in the Noidmifs directory, give it a relevant name (addclass1.mif) and insert something like this:

    Start Component
       Name = "System Information" Start Group
          Name = "Wide World Asset Numbers" ID = 1
          Class = "wideWorldAssetNumbers" Key = 1
          Start Attribute
             Name = "Computer Asset Number" ID = 1
             Type = String(10)
             Value = "414207" End Attribute
       End Group
    End Component

    This would create a class called wideWorldAssetNumbers in your Hardware Inventory. For more info, see http://technet.microsoft.com/en-us/library/cc181210

    If I now run a Hardware Inventory on the client I’ll see in the InventoryAgent.log that it was processed (I’m running this on a Site Server by the way, that's why the path is SMS_CCM\Inventory)

    image

    And if I check the hardware inventory on the client, I’ll now see a new class called Wide World Asset Numbers

    image

    You can also see a new table in the ConfigMgr database

    image

    And that’s how easy it is to create a new Hardware Inventory class, and a new ConfigMgr database table!

    Matt Shadbolt

  • ConfigMgr 2012 SP1: Deploy iOS and Android Apps!

    With all of the excitement surrounding the Beta 1 release of ConfigMgr 2012 SP1, there’s been a fairly big feature that's been rarely spoken about… Deploying iOS/Android apps to ‘un-managed’ devices!

    This post wont be a deep dive into creating and deploying iOS/Android apps, it will just take you through the high-level announcements and give you something to start thinking about before SP1 hits RTM.

    Firstly, you’ll want to check out the iOS app demo from the presentation made by Brad Anderson at TechEd Europe. The demo shows an iOS device using the Intune service to access and install a custom LOB (Line of Business) application.

    http://channel9.msdn.com/Events/TechEd/Europe/2012/KEY01 (1 hour 27 into the video for those playing at home)

    Secondly, you’ll want to download and test the Beta 1 release of ConfigMgr 2012 SP1

    http://www.microsoft.com/en-us/download/details.aspx?id=34607

    NOTE: This is full installation media. You don’t need to build an RTM server and upgrade. You do however, need to install the new WADK separately, otherwise the prereq check will fail.

    ConfigMgr 2012 makes the deployment a snap, because all we need to do is add a new Deployment Type to our current applications. This means we can have a user receive the LOB app via MSI if they’re in Windows, and the iOS app if they request it on their iPhone. You can really see the benefit of the new ConfigMgr 2012 App Model when you think about all your users utilizing different devices and different deployment types… it’s really rather exciting.

    image

     

    The process flow would be:

    image

     

    In terms of installing the application, the application would be delivered via a pull function. That is, we can’t forcibly install the application on a target iOS device, but instead we make the application Available for our users to install.

    The process flow would be:

    image

     

    Finally, I wanted to add a couple of screenshots – one from the iOS client and one from the ConfigMgr console.

    1. Creating a new iOS Deployment Type

    image

    2. Installing the App on an iOS device

    image image

     

    There will be HEAPS more details coming soon… so stay tuned!

    Matt

  • ConfigMgr 2012 – Where’s my PXE CacheExpire gone!?

     

    In ConfigMgr 2007 we had a registry key called CacheExpire which would allow a client to start a new PXE session after 60 minutes. The idea is, if a build is mandatory the cache will hold onto the session to ensure it doesn’t get into a rebuild loop.

    It was a bit of a pain when you were developing/testing your OSD builds because if it failed, you had to wait for the cache to run out or clear it manually. So many engineers would change the key to 120 seconds or so.

    HKLM\Software\Microsoft\SMS\PXE\ CacheExpire=120

    I’ve recently been testing a new build in ConfigMgr 2012 using PXE as my boot method, and went in search of the CacheExpire value to speed up the process, and found its no longer there. In fact, the entire PXE key is missing.

    The reason is quite simple, in ConfigMgr 2012 the PXE Service Point is no longer a separate role – it’s now integrated with the Distribution Point role. So I checked in the DP registry key for a CacheExpire… no luck.

    HKLM\Software\Microsoft\SMS\DP

    So I decided to try and create one and see how it went… bingo, my PXE Cache is now 120 seconds.

    Fox the lazy, here’s the exported key & value

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP]
    "CacheExpire"="120"

    Matt Shadbolt

  • PFE's at TechEd Australia 2012!

    SMIC1417_email-signature_-Speaking_v2

     

    Heaps of PFE’s speaking at this years TechEd Australia!

     

    Ian Bartlett & Mohnish Chaturvedi – Microsoft Application Virtualization 5.0 Introduction (Wed 12 Sep, 9:45-11:00)

    Grant Holliday – From Server to Service: How Microsoft Moved Team Foundation to Azure (Thu 13 Sep, 11:30-12:45)

    Matt Shadbolt & George Smpyrakis – Implementing SCM for Compliance in SCCM 2012 (Thu 13, 1:45-3:00)

    Alex Pubanz & Jesse Suna – Kick Starting your Migration to Windows Server 2012 (Friday 14 Sep, 8:15-9:30)

    Chad Duffy & Tristan Kington DirectAccess: Your Next Gen Remote Access Experience (Fri 14 Sep, 11:30-12:45)

    Shyam Narayan – Application Hosting Models in SharePoint 2013 (Fri Sept 14, 11:30-12:45)

  • Trace32.exe/CMTrace.exe Hidden Features

    So I posted this on my mattlog.net blog ages ago, but for some reason it didn’t make the migration over to our new Technet ConfigMgrDogs blog, so thought I should repost as a new entry.

    I still find it staggering how many customers I visit who had no idea about these features!


    Trace32’s Error Lookup feature.

    One of the more important but commonly missed features is the Error Lookup option in Trace32’s Tools > Error Lookup (Ctrl + L) menu.

    image

    The Error Lookup tool will return descriptions of cryptic error codes from

    Windows error codes

    image

    image

    WMI error codes

    image

    image

    Winhttp error codes

    image

    Trace32’s Merge selected files feature.

    When trying to troubleshoot specific issues such as site replication issues, it’s sometimes nessesary to open more than one log file at once. Windows 7’s window snap feature makes viewing two logs side-by-side really easy, but sometimes a more accurate timeline is needed between viewing log files.

    If you select Open in Trace32, Ctrl-click on multiple log files in the open dialog box, tick Merge selected files you will find that all the selected log files will merge together into one large super log. The log entries are automatically sorted by time so it’s super easy to see ConfigMgr process certain things and log the progress across multiple logs.

    In this quick example I’m just viewing the process for finding a clients default management point

    image

    As you can see, the client is logging to both LocationServices.log and ClientLocation.log and it’s quite easy to read the timeline of what is going on.

    Trace32’s Last Directory registry key.

    Lastly, a minor but handy tip, Trace32 by default will save the last log location that you opened. This is really handy as you don’t have to browse to the logs path every time you want to read SMS logs. It is a bit of a pain though when you use Trace32 on a client, because every time you launch Trace32 for the first time on a certain machine, it defaults to the %userprofile%\Desktop directory. The Last Directory registry found at HKCU\Software\Microsoft\Trace32 is the key that controls the default open location. If you add a GPO that updates your clients to %windir%\System32\CCM\Logs\ every time you jump on a machine it will automatically open Trace32 at the client log location.

  • ConfigMgr 2012: Upcoming Enhancements in SP1

    The Product Group have recently announced the Beta of ConfigMgr 2012 SP1 at TechNet 2012 North America.

    You can view the announcement at http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/MGT309 

    Enhancements include:

    • Platform Support:
      • Windows 8
      • Windows 8 tablet (Intel SoC) support
      • Mac OS X
      • Linux and Unix
    • Operating System Deployment: Windows To Go support
    • Application Delivery:
      • Win 8 apps
      • Deep link applications
      • Network Cost Support
    • PowerShell Provider
    • PowerShell Cmdlets:
      • Tasks exposed in the Administration Console
      • Suitable experience for administrator (not the SDK)
      • Align with PowerShell general contentions
    • Bitlocker changes:
      • TMP and PIN
      • Used Space Bitlocker
    • Prestaged media now supports additional content
      • WIM, Applications, Drivers, Package/Programs
    • Flexible hierarchy management:
      • Ability to add a new Central Administration Site
      • Migration between ConfigMgr 2012 hierarchies
    • Hierarchy easier to control:
      • Schedule replication for a given link
      • SQL Server distributed views
      • Compression for SQL Server data
    • Software Updates Management:
      • Fallback to Windows Update for content
      • Definition updates 3x/day
    • Endpoint Protection
      • Real-time administrative actions
    • Settings Management: User Profile and Data Management
      • Client Side Caching
      • Roaming User Profiles
      • Folder Redirection

    image

    image

    image

    image

    Matt Shadbolt

  • My Experience Upgrading to CM12 SP1

     

    Hi All, it’s been a while since my last post and one of Matts posts hit-count just past my article on Auto Deployment Rules  (Unashamed plug of my old blog post to try and get the numbers up). So I decided, okay it’s time to get another one done.

    NOTE: This is not meant to be a step by step guide merely some general advice and run through. I always recommend doing any upgrade process in your test lab environment before even considering upgrading in production. If you don't have one create one.

    The environment I'm working with is a lab that was setup when ConfigMgr 2012 RTM came out. It sits on Server 2008 R2 SP1 and SQL 2008 R2 SP1 CU4. Probably not too dissimilar to most 2012 RTM environments.
    I have a one CAS, one Child Primary and one Secondary Site.

    The first thing I want to do is run the prerequisite checker.
    On the ISO I have Prereqchk.exe sits in the folder SC2012SP1_RTM_SCCM_SCEP\SMSSETUP\BIN\X64.

    clip_image001[1]

    The advantage of running this instead of running through the setup GUI and then seeing what prerequisites are required, you avoid having to have to exit the setup and run through the entire setup process again. To get the command line switches simply run prereqchk /?

    Let's run it on each server separately to see what is needed.
    CAS Server (CM12CAS.Contoso.com)
    Open an administrative command prompt and run the following command

    prereqchk /CAS /SQL <FQDN of the SQL Server>  /SDK <FQDN of the SDK Server>

    Feel free to add any other switches that you would like to but this will server our current purpose.

    clip_image002[1]

    clip_image003[1]

    clip_image004[1]

    OK so we can see a couple of Warnings which I expected in our lab environment, and number of things we need to fix.
    Anything that is a warning is usually just a best practice alert such as the WSUS on site server warning, or for you to be aware of a potential issue such as verifying site server permissions to publish to AD.
    Let's go through the errors.

    1) We can ignore the two errors Existing Configuration Manager server components on site server and Dedicated SQL Server Instance because the prereqchk is assuming we are trying to do a fresh install on this site server, not an upgrade.
    2) User State Migration Tool(USMT) installed, Windows Deployment Tools installed and Windows PreInstallation Environment installed are all part of the latest Window Assessment and Deployment Toolkit which you can download from here http://www.microsoft.com/en-us/download/details.aspx?id=30652
    3) SQL Server version I need to upgrade SQL from 2008 R2 SP1 CU4 to either CU6 or SP2. (See Supported Configurations for Configuration Manager.)

    NOTE : f you are going to upgrade from 2008 RTM/R2 to SQL 2012 post upgrading to ConfigMgr 2012 SP1, you need to upgrade in the following order.
    1st - CAS
    2nd - Secondary Site
    3rd - Child Primary of that secondary site.

    From Technet - http://technet.microsoft.com/en-us/library/gg682077#BKMK_SupConfigUpgradeDBSrv

    For Configuration Manager SP1 only: Configuration Manager with SP1 supports the in-place upgrade of SQL Server 2008 or SQL Server 2008 R2 to SQL Server 2012 with the following limitations:

    •        Each Configuration Manager site must run service pack 1 before you can upgrade the version of SQL Server to SQL Server 2012 at any site.

    •        When you upgrade the version of SQL Server that hosts the site database at each site to SQL Server 2012, you must upgrade the SQL Server version that is used at sites in the following order:

    o        Upgrade SQL Server at the central administration site first.

    o        Upgrade secondary sites before you upgrade a secondary sites parent primary site.

    o        Upgrade parent primary sites last. This includes both child primary sites that report to a central administration site, and stand-alone primary sites that are the top-level site of a hierarchy.

    Important

    Although you upgrade the service pack version of a Configuration Manager site by upgrading the top-tier site first and then upgrading down the hierarchy, when you upgrade SQL Server to SQL Server 2012, you must use the previous sequence, upgrading the primary sites last. This does not apply to upgrades of SQL Server 2008 to SQL Server 2008 R2.

    4) If you haven't already done so, the following WSUS Updates may also need to be applied.
    An update for Windows Server Update Services 3.0 Service Pack 2 is available (KB2734608)
    An update for Windows Server Update Services 3.0 Service Pack 2 is available (KB2720211)
    PLEASE read and understand what may occur in your environment before applying these hotfixes. and of course test in your lab environment first.

     

    Install WADK


    Ok so let's install the WADK components to my CAS
    Download it from the link above
    Run adksetup
    Download the Kit to a network location so it is available for installation. (Note this may take a while)

    clip_image005

    From that location on your server share
    Run adksetup.exe
    Specify your installation directory and click Next

    clip_image006

    Select Yes or No depending on your preference and click Next

    clip_image007

    Accept the license agreement

    clip_image008

    All you should need is the Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tool (USMT) select these and click Install

    clip_image009

    Again, this may take a while to install.

    NOTE: Check your build via PXE after this is done as you may potentially need to remove and redistribute your x64 Boot Image. Ensure you refer to the SMSPXE.log file for any errors.

     

    SQL Upgrade
    I'm going to upgrade to SQL 2008 R2 SP2.
    (If you wish to do the same you can get SP2 from here How to obtain the latest service pack for SQL Server 2008 R2)

    Run the SP2 executable

    clip_image010

    Click Next

    clip_image011

    Accept the license agreement

    clip_image012

    Click Next

    clip_image013

    After the file check click Next

    clip_image014

    Click Update

    clip_image015

    Click Close

    clip_image016

    Click OK and restart the server
    I'd suggest checking the SQL Logs after the reboot to ensure there are no errors that you may need to look into.

    Upgrade to ConfigMgr to SP1

    Now we can start the SP1 Upgrade

    Double click on splash.hta to bring up the splash screen

    clip_image017

    You'll see a familiar screen Click Install

    clip_image018

    Click Next

    clip_image019

    Select Upgrade this Configuration Manager Site and Click Next

    clip_image020

    Enter your product key and click Next

    clip_image021

    Accept the license agreement and click Next

    clip_image022

    Accept the license agreement and click Next

    clip_image023

    You can either download the latest prerequisite files from the internet and save them on a network location, or use an already downloaded copy. In this case they are available on my copy of the ISO so I'll just grab them from there. Obviously over time I'd suggest you download the latest version from the internet.

    Click OK and Next

    clip_image024

    Select your Server Language and click Next

    clip_image025

    Select your client language and click Next.

    clip_image026

    Click Next again at the Summary screen

    clip_image027

    Finally we reach the prerequisite check screen (You can now see the value in using prereqchk.exe)
    For more detail you can look at the ConfigmgrPrereq.log file in the root of C.

    Click Begin Install

    clip_image028

    You should now see a log file called C:\ConfigmgrSetup.log open this up to watch how the upgrade process is going.

    clip_image029

    We can see that after a successful connection to the database we are about to Upgrade the CAS Server

    clip_image030

    After about 40 minutes in my lab the upgrade process is complete. See the entry in the setup log file above

    clip_image031

    We can now click Close on the splash screen

    clip_image032

    Now let's check and see if the Site has upgraded successfully.
    Open the ConfigMgr console and select Administration > Site Configuration > Sites > CAS right click and select Properties

    clip_image033

    As per Matt’s previous blog we can now see that our CAS is at Version 5.00.7804.1000 and Build number 7804

    clip_image034

    I'm also going to check my database replication and ensure everything is functioning correctly. .
    One other thing that is interesting to note is the change in the change in the configure Client Installation Settings under Administration > Sites and in the ribbon Hierarchy Settings

    RTM

    clip_image035

    SP1

    clip_image036

    We now no longer have a choice to select the latest version for the Automatic Client Upgrade option.


    Child Primary

    OK, so let's now move onto the Child primary

    Open an administrative command prompt and run the following command

    prereqchk /PRI /SQL <FQDN of the SQL Server>  /SDK <FQDN of the SDK Server>

    clip_image037

    So we can see the exact same prereqs as the CAS, so I will run through the same process as per the CAS of installing the latest WADK and upgrading SQL.

    Upgrade to SP1

    The screen shots are exactly the same for the child primary so I won't bore you with those

    clip_image038

    Once we start again, we can see in the Setup log file after the SQL connections are successful the upgrade will begin

    clip_image039

    Then after about 30 minutes we can see that the setup is now complete

    clip_image040

    We can also see a few extra tasks have been done on the Child Primary.

    Let’s check some of the logs and the console to ensure it has upgraded successfully.

    clip_image041

    To see if the components have reinstalled without issue, we can check the sitecomp.log under <SCCMInstallFolder>\Logs
    We can see where the bootstrapper starts successfully after SP1 finishes installing. You can also see as it successfully reinstalls each component.

    See the figure below for all of the entry’s filtered in the log file.

    clip_image042

    clip_image043

    You may also notice a few new components being installed.

    clip_image044

    Mpcontrol.log shows us that the management point is communicating successfully.

    Now jump into the console and check the site version and database replication. We also essentially check that the provider is functioning since we need it to be to get into the console.

    clip_image045

    All looks good. Also the picture of the Cloud is a bit of a giveaway.

    clip_image046

    DB Replication also looks nice and healthy.


    Secondary Site

    OK, so now lets look at our Secondary site

    Open an administrative command prompt and run the following command

    prereqchk.exe /SECUPGRADE

    clip_image047

    We can see that there are 2 points I need to fix before attempting an upgrade.

    1) The upgrade process will not automatically install a supported version of SQL so we need to do it manually first
    2) SQL Express does not have a static port set so we will need to go into SQL to set a static port of 1433.

    The upgrade of SQL we have already run through so I will just go through setting the static port
    On the secondary server open up SQL Server Configuration Manager

    clip_image048

    Ensure the local Secondary server is selected (Or remote server name if you've started it from another server)

    clip_image049

    Expand SQL Server Network Configuration and select Protocols for CONFIGMGRSEC
    Then double click on TCP/IP under protocol name

    clip_image050

    You will notice that SQL has both Dynamic and a static port set for IPAll

    clip_image051

    Lets delete the Dynamic entry and click Apply

    clip_image052

    Click OK and restart the appropriate services.
    After I have upgraded SQL and changed the port I run my prereq check again.

    clip_image053

    We can now see that the errors are gone and we should be able to upgrade our secondary site successfully. You also may have noticed that I have warnings on all of the servers for SQL Server process memory allocation. That is because SQL requires a minimum of 8 GB of RAM for a CAS and Primary, and 4GB for a secondary. It will still run with less as per my Lab VM’s but you will get a performance hit.

    Upgrade to SP1

    As most of you will now know we install and we upgrade the Secondary site via the ConfigMgr console and not directly on the box itself.
    So we can open the console on either our CAS or our Child Primary. I'll do it from the Child primary just to speed things up.

    clip_image054

    Go to Administration > Sites and select the secondary site. You will now see an Upgrade option available on the ribbon.
    When your upgrading you have two choices to monitor what is happening.
    1) Click on Show Install Status

    clip_image055

    This brings up a step by step guide to let you know at what stage the installation is at. Here we can see that the prereq’s have already occurred and the Bootstrap service has already been installed ready for the upgrade.

    2) Look at the local log files sitting in the root of C:\

    clip_image056

    As with the CAS and the Child primary, we have the exact same prereq Wizard and setup log files that go into much more depth should there be any issues with the installation. Although we will need to watch the logs initially on the Child Primary before the setup and bootstrap begins on the secondary site.

    clip_image057

    I will click on Upgrade get the above warning then click Yes.

    clip_image058

    This log file is from the Child Primary

    clip_image059

    With each action we can see the corresponding action in the appropriate log file if we wish.
    Once prereqs are finished we can see that the bootstrapper begins its process

    clip_image060

    clip_image061

    And on the secondary site we can see the upgrade process begin

    clip_image062

    clip_image063

    clip_image064

    clip_image065

    And we can see that now the installation is complete

    clip_image066

    clip_image067

    I'm going to check the SMSEXEC.log to see if my components have started.

    clip_image068

    I'm also going to check MPControl.log to see if my management point is functioning as expected.

    clip_image069

    Now ill check the version and database replication status from the console.

    clip_image070

    We can see that we are on build 7804

    clip_image071

    And we can also see that database replication is working as expected.

    I would suggest checking that all of your components on each server, are functioning correctly. Keep your eye on the status messages and alerts, in case any of them fail and need further attention. You can do this from Monitoring > Site Status and Component Status. Below we can see an example of an issue with my Software Update Point after the SP1 update  that needs attention.

    image   
    Looking at the WCM.LOG you can see that I haven't applied the WSUS updates I mentioned earlier in this blog.

    An update for Windows Server Update Services 3.0 Service Pack 2 is available (KB2734608)
    An update for Windows Server Update Services 3.0 Service Pack 2 is available (KB2720211)

    image

    I will download and apply these updates.

    after a restart of the WSUS Configuration Manager component (This isn't necessary the next time it polls it would do this anyway) you can see that it now has a supported version and is now running though setting up the updated component.

    image

    Conclusion and next steps.

    So what we have seen here are various methods to run through the upgrade process and various log files and GUI settings in the console that we can use to follow the process. If you plan and get the prerequisites setup correctly before you begin you should have a fairly smooth SP1 upgrade.

    Next steps.
    1) Update your ConfigMgr Client package to all of your Distribution points and plan out the client upgrade.
    2) Think about and potentially plan an upgrade to SQL 2012.

    George Smpyrakis

  • How to find SCCM duplicate computer objects

    One of the many tasks an SCCM admin faces is checking for ConfigMgr duplicate computer records. There are many ways that we can get duplicate records, but here are the three most common:

    Duplicate MAC Addresses.

    I normally see this in environments where VDI is common. Generally, a VDI admin has duplicated machines without giving each a unique MAC address. This is bad and should be avoided. If you’re VDI admin has created a bunch of computers with the same MAC, we need to delete them from SCCM. To find these objects, run the following TSQL query:

    SELECT dbo.v_RA_System_MACAddresses.MAC_Addresses0, Count(dbo.v_R_System.Name0) AS SystemCount 
    FROM dbo.v_R_System RIGHT OUTER JOIN dbo.v_RA_System_MACAddresses
    ON dbo.v_R_System.ResourceID = dbo.v_RA_System_MACAddresses.ResourceID
    GROUP BY dbo.v_RA_System_MACAddresses.MAC_Addresses0 ORDER BY SystemCount DESC
    Duplicate Computer Names.

    These are the most common duplicate objects. Most likely this occurs due to OSD or conflicting discovery cycles. We basically end up with two computer objects, with the same name/hardware/MAC but different SMSBIOSGUID. It causes much confusion for ConfigMgr because it often doesn’t know how to process the inventory for the phantom object. To find these objects, create an SCCM Query (or query based collection) with the following Query Statement:

    select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,
    R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r 
    full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId 
    full join SMS_R_System as s2 on s2.Name = s1.Name 
    where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId
    Duplicate HardwareID’s

    One other way to look for dupes is to use the HardwareID. Use the following TSQL to find the objects with duplicate HardwareIDs:

    SELECT Name0, Hardware_ID0, Count(Hardware_ID0) AS SystemCount
    FROM dbo.v_R_System
    GROUP BY Hardware_ID0, Name0
    ORDER BY SystemCount DESC
     
    Matt Shadbolt
  • SCCM 2012 Beta 2: setupdl.exe doesn’t launch

    Had an annoying one this afternoon. While trying to install the new (ish) SCCM 2012 Beta 2 the Updated Prerequisite Components wizard wouldn’t download the prereqs. I was able to run the setupdl.exe manually, but still when providing the prereq path to the Updated Prerequisite Components wizards it would still fail.

    <04-28-2011 14:38:50> INFO: setupdl.exe: Start
    <04-28-2011 14:38:50> INFO: setupdl.exe: Finish

    Really easy fix in the end. You just need to make sure the prereqs are stored in a directory without any spaces in the name, and bingo. :/

    Matt Shadbolt

  • ConfigMgr 2012 Content Library Overview

    Content Management in ConfigMgr 2012 has completely changed to what we did in SCCM
    2007.

    When you distribute content to a Distribution Point in ConfigMgr 2012, a check is done against the Content Library to confirm that any of the source files being referenced in your application/package do not already exist in the Content Library. Ie. There is only one copy of every file stored on a DP regardless of how many packages reference that one file.

    The SCCMContentLib Directory

    The ConfigMgr 2012 Content Library (SCCMContentLib) consists of 3 subfolders:

    1. PkgLib
    2. DataLib
    3. FileLib

    1. PkgLib

    In the Package Library folder you will find a PackageID.ini file for every package. The PackageID.ini file for each package will give you the details for the Data library content and what file you will need to look for.

    2. DataLib

    In the Data Library folder you will find a PackageID.ver.ini file for each package and a PackageID.ver folder. The folder is a “copy” of the exact package folder structure but without any of the real files. For each file in the original package you will find a corresponding .INI file with information about the original file. To find the HASH value for the file you are interested in, open the relevant .INI file and make a note of the first 4 digits of the HASH value, this will be needed to find the data in the FileLib directory

    3. FileLib

    The File Library folder is where you will find the actual files that are used in the different packages. All files are grouped together in a folder. The folder for each file uses a 4 digit pre-fix of the HASH value of that file found in the DataLib. The FileLib is where the nuts and bolts of the application are stored. You will see three files under each folder:

    1. A file with no extension (FILE), the actual file named is the HASH value. This file
    contains all of the source files for that part of the application. If the
    application only had a single .EXE or .MSI file to execute than you could copy
    the file to a location such as the Desktop, rename it to the original file name,
    ie .EXE, .MSI and start the installation

    2. Hash.ini file contains a link between the file and the packages that uses the file. If you have multiple
    packages referring the same file, you will just see an entry for each package
    ID.

    3. Hash.sig. It contains the original package signature

    ConfigMgr 2012 Content Library in Action…

    For this example I will use my Microsoft Office 2010 package which has Package ID IBC0000B.

    1. Navigate to the SCCMContentLib directory on your DP.

    2. open the PkgLib directory 
    Content Library 1
    Content Library 2

    3. Open the configuration file referencing your Package ID, ie IBC0000B, and make a note of the ContentID it is referencing, ie Content_30b777f9-be…………..
    Content Library 3

    4. Navigate to SCCMContentLib\DataLib and open the directory that was referenced in your package configuration file, ie Content_30b777f9_30b777f9-be51-484b-8327-77bf2ef75169.1
    Content Library 4

    Notice that folder Content_30b777f9_30b777f9-be51-484b-8327-77bf2ef75169.1 holds reference to all files in your source location, ie you will see all the Office 2010 files being referenced. NOTE: These files do not contain any of the actual source data, only references to the HASH values for each

    Content Library 5

    5. Open any of the configuration files referencing a file in your package to gain the HASH value to the actual content. For this example I will use the setup.exe file as the example.
    Content Library 6

    6. Take note of the first 4 digits in the hash, so for the setup.exe file it will be “97E6”

    7. Navigate to SCCMContentLib\FileLib\<4 digit hash> -  eg SCCMContentLibrary\FileLib\97E6
    Content Library 7

    8. The file with extension ‘FILE’ is the actual content for the setup.exe file in our source content. To confirm this we can see the size of this file is 1075KB, the same as our setup.exe file from our source location.OriginalSource Files
    Content Library 8

    9. As this Office is an application made up of many components, ie Word, Excel etc, they all share common files; to see what packages require the setup.exe file you could open the “Configurations Settings” file to see the package IDs of all packages that require the setup.exe file.
    For applications that are compiled to one executable, eg Adobe Reader, you could follow this process and simply copy the FILE file to a desktop, set the file extensions accordingly, ie .EXE and you could simply run this file and it would execute and install as it would contain all source files…

    THAT’S IT…  GOOD LUCK…

  • Include/Exclude Collections Rule

    My last post on ConfigMgr 2012 Collections (I promise!). I wanted to go over Include and Exclude Collection Rules.

    Include and Exclude collection rules are a new feature in ConfigMgr 2012 and I think you’ll find them most useful. They basically allow us to add or remove resources from a collection without having to write a complex membership rule.

    Let’s say we have five collections: Finance Accountants, Finance Banking, Finance Bookkeeping, Finance Insurance and Finance Interns. Each of these collections will have their own Deployments targeted at the users in the collections. If we wanted to target an application at all of these collections, we would need to have 5 deployments.

    Or we could create a collection with an Include Collection setting



    Now we can just target the application at the Finance – All collection and we’ll get all three members.

    Exclude collections are even cooler. Let’s say we have a collection for all computers who need Office 2010. Normally we would just deploy our application to the collection and hope for the best. We can use an Exclude Collections rule to be a little smarter in our deployments and remove all clients who are in an ‘unhealthy’ state.

    First, we’ll create our Unhealthy Clients Collection. Our membership rule will be any looking for any client who’s client status is NULL or the client activity is NULL. This should get any computer that hasn’t got the client installed, or any computer with the client installed that isn’t active. (this is a *really* basic query for unhealthy clients. You can write a more complex one to find those clients who are truly unhealthy)


    I’ve got 4 systems in my lab hierarchy – only one of which is healthy (oh, and the two Unknown Computer objects – but they don’t count)

    So when I update the membership of my Office 2010 membership, I will only get the healthy client.

    Using this exclusion method has a few benefits – firstly, you have a collection full of systems in which you have to repair the ConfigMgr client. Secondly, you’re software deployment statistics should be a lot cleaner as you’re not getting failures on the unhealthy clients. Finally, as the collection is dynamic, as soon as you remediate the unhealthy clients, they will receive the Office 2012 deployment!

    Matt Shadbolt

  • IIS ODBC Logging Event ID 1016 (error data 80070057)

    “The World Wide Web Publishing Service (WWW Service) did not configure logging for site X. The data field contains the error number.”

    This warning will show up in your System event logs and you custom IIS logging to a SQL database won’t work. Obviously the message is fairly cryptic, however in a facepalm sort of moment I worked out what wasn’t working.

    Two words. Custom Logging.

    Although I had enabled the ODBC logging feature for IIS, I hadn’t enabled custom Logging. Once you enable the custom logging feature your SQL DB will start to fill with log entries. I’ve included the full warning message for those of you unsure.

    “The World Wide Web Publishing Service (WWW Service) did not configure logging for site X. The data field contains the error number.”

    This warning will show up in your System event logs and you custom IIS logging to a SQL database won’t work. Obviously the message is fairly cryptic, however in a facepalm sort of moment I worked out what wasn’t working.

    Two words. Custom Logging.

    Although I had enabled the ODBC logging feature for IIS, I hadn’t enabled custom Logging. Once you enable the custom logging feature your SQL DB will start to fill with log entries. I’ve included the full warning message for those of you unsure.

    <Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event>
    <System>
    <Provider Name=”Microsoft-Windows-IIS-W3SVC Guid=”{05448E22-93DE-4A7A-BBA5-92E27486A8BE} EventSourceName=”W3SVC />
    <EventID Qualifiers=”32768>1016</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0×80000000000000</Keywords>
    <TimeCreated SystemTime=”2009-04-15T23:55:39.000Z />
    <EventRecordID>46323</EventRecordID>
    <Correlation />
    <Execution ProcessID=”0 ThreadID=”0 />
    <Channel>System</Channel>
    <Computer>SERVER01</Computer>
    <Security />
    </System>
    - <EventData>
    <Data Name=”SiteID>3</Data>
    <Binary>57000780</Binary>
    </EventData>
    </Event>
     
    Matt Shadbolt
  • Package & Application Source Modification Scripts

    I promised in my last post to provide you all with my scripts for modifying all your package and application source paths… well that was over two months ago now!

    http://blogs.technet.com/b/configmgrdogs/archive/2013/02/18/moving-your-package-source-after-migration.aspx

    Note: These scripts are provided “as-is” and no guarantees are provided. Please TEST these in a non-production environment beforehand.

     

    ApplicationSourceModification.ps1 (Version 1.0)

    First is my script will modify the source paths for all of your Deployment Types within all Applications that are Script or MSI installers (you can modify this to do your App-V Deployment Types too)

    Write-Host "#######################################################################" -f Green
    Write-Host "##        Matts ConfigMgr 2012 SP1 Application Source Modifier       ##" -f Green
    Write-Host "##                blogs.technet.com/b/ConfigMgrDogs                  ##" -f Green
    Write-Host "##                                                                   ##" -f Green
    Write-Host "##                                                                   ##" -f Green
    Write-Host "##  Please ensure your package source content has been moved to the  ##" -f Green
    Write-Host "##          new location *prior* to running this script              ##" -f Green
    Write-Host "##                                                                   ##" -f Green
    Write-Host "#######################################################################" -f Green
    Start-Sleep -s 2

    Write-Host ""
    Write-Host ""
    ## Import ConfigMgr PS Module
    Import-Module 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1'

    ## Connect to ConfigMgr Site
    $SiteCode = Read-Host "Enter your ConfigMgr Site code (XXX)"
    $SiteCode = $SiteCode + ":"
    Set-Location $SiteCode
    Write-Host ""

    ## Set old Source share
    Write-Host "NOTE: This is the location your 2007 packages are stored. It must be correct"
    $OriginalSource = Read-Host "Enter your source ConfigMgr share (\\2007Server\Source$)"

    ## Set new Source share
    Write-Host ""
    Write-Host "NOTE: This is the location your Applications are stored. It must be correct"
    $DestinationSource = Read-Host "Enter your destination ConfigMgr Source share (\\2012SERVER\Source$)"
    Write-Host ""
    Write-Host "Working.."
    Write-Host ""
    ## Get your Application Deployment Types

    $ApplicationName = Get-CMApplication
    $ApplicationName = $ApplicationName.LocalizedDisplayName

    ForEach($x in $ApplicationName)
    {
    $DeploymentTypeName = Get-CMDeploymentType -ApplicationName $x
    #$DeploymentTypeName = $DeploymentTypeName.LocalizedDisplayName

        ForEach($DT in $DeploymentTypeName)
        {
        ## Change the directory path to the new location
        $DTSDMPackageXLM = $DT.SDMPackageXML
        $DTSDMPackageXLM = [XML]$DTSDMPackageXLM
       
        ## Get Path for Apps with multiple DTs
        $DTCleanPath = $DTSDMPackageXLM.AppMgmtDigest.DeploymentType.Installer.Contents.Content.Location[0]
       
        ## Get Path for Apps with single DT
        IF($DTCleanPath -eq "\")
        {
            $DTCleanPath = $DTSDMPackageXLM.AppMgmtDigest.DeploymentType.Installer.Contents.Content.Location
        }
       
        $DirectoryPath = $DTCleanPath -replace [regex]::Escape($OriginalSource), "$DestinationSource"

        ## Modify DT path
        Set-CMDeploymentType –ApplicationName "$x" –DeploymentTypeName $DT.LocalizedDisplayName –MsiOrScriptInstaller –ContentLocation "$DirectoryPath"
       
        ## Write Output
        Write-Host "Application " -f White -NoNewline;
        Write-Host $x -F Red -NoNewline;
        Write-Host " with Deployment Type " -f White -NoNewline;
        Write-Host $DT.LocalizedDisplayName -f Yellow -NoNewline;
        Write-Host " has been modified to " -f White -NoNewline;
        Write-Host $DirectoryPath -f DarkYellow
        }
    }

    PackageSourceModification.ps1 (Version 1.0)

    My second script is much simpler, as we are changing only the Package source location, with no need to cycle through each Deployment Type

    Write-Host "#######################################################################" -f Green
    Write-Host "##        Matts ConfigMgr 2012 SP1 Package Source Modifier           ##" -f Green
    Write-Host "##                blogs.technet.com/b/ConfigMgrDogs                  ##" -f Green
    Write-Host "##                                                                   ##" -f Green
    Write-Host "##                                                                   ##" -f Green
    Write-Host "##  Please ensure your package source content has been moved to the  ##" -f Green
    Write-Host "##          new location *prior* to running this script              ##" -f Green
    Write-Host "##                                                                   ##" -f Green
    Write-Host "#######################################################################" -f Green
    Start-Sleep -s 2

    $SiteCode = Read-Host "Enter your ConfigMgr Site code (XXX)"
    $SiteCode = $SiteCode + ":"
    Set-Location $SiteCode

    $PackageArray = Get-CMPackage
    $OldPath = "\\2007SERVER\source$"
    $NewPath = "\\2012SERVER\cmsource$"
    ForEach ($Package in $PackageArray)
    {
    $ChangePath = $Package.PkgSourcePath.Replace($OldPath, $NewPath)
    Set-CMPackage -Name $Package.Name -Path $ChangePath
    Write-Host $Package.Name " has been changed to " $ChangePath
    }

    Matt Shadbolt

  • ConfigMgrDogs at TechEd Australia!

    SMIC1417_email-signature_-Speaking_v2

    Your ConfigMgrDogs team will be speaking at TechEd Australia 2012!

    Come and check out our sessions & buy us a beer!

    Matt Shadbolt and George Smpyrakis – Configuration Manager 2012 and Security Compliance Manager

    Ian Bartlett and Mohnish Chaturvedi – Introduction to App-V 5.0

     

    Session time and room information will be posted shortly.

     

    Matt Shadbolt

  • Software Update Compliance Reports – Detection State Unknown

    I have been working with a number of customers recently that have had issues running their monthly Software Update compliance reports due to a high number of “DETECTION STATE UNKOWN” results reporting back long after the update deployment has successfully run.

    As usual the first thing we want to identify is whether it is on the client side or server side.

    State Message IDs are used to define specific state messages for each topic type. For our issue a State Message for a Software Updates has a TopicType=500 which has status Message ID state of 0, 1, 2 or 3 which would then depict the actual state of the given update on a client machine as below:

    Topic Type

    State Message ID

    State Message Description

    500

    0

    Detection state unknown

    500

    1

    Update is not required

    500

    2

    Update is required

    500

    3

    Update is installed

    To determine what information your clients are sending back to your Management Point we can use WMI queries to see what is happening on the client.

    1. Open wbemtest with elevated permissions

    image

    2. Connect to the WMI Namespace: root\CCM\StateMsg

    image

    3. Select Query and run the query  SELECT * FROM CCM_StateMsg

    image

    image

    Find any software update deployment which can be determined by looking for “TopicType=500” and what we want to check is the below values in yellow as this will determine if the client has indeed sent a message back to the MP and if so what it sent back, If we see it sent back a “0” and confirm that the KBs are installed then we know it is something on the client side, we would expect to see 1, 2 ,3 pending the state listed above

    image

    image

    image

    image

    Example below:

    instance of CCM_StateMsg

    { Criticality = 0;

    MessageSent = TRUE;      Message is sent

                                                MessageTime = "20101027211908.749000+000";           UTC Time

                                                ParamCount = 1;

                                                StateDetails = "";

                                                StateDetailsType = 0;

    StateID = 2;   Update is required

                                                TopicID = "9d4681d5-46fa-4250-bedc-480ac7bce3aa";

                                                TopicIDType = 3;

    TopicType = 500;   Update Detection

                                                UserFlags = 0;

                                                UserParameters = {"102"};

    Hope this helps..

  • Teched Australia 2013: Powershell for ConfigMgr 2012 SP1

     

    SMIC1608_blogBling_speaking For the second year running, I’ll be speaking at the Teched Australia 2013 conference on the Gold Coast, Australia.

    The session will cover the Powershell integration into ConfigMgr 2012 SP1.

    I’ll be posting all the scripts, video and transcript after the event.

    Hope to see you there!

    Powershell for ConfigMgr 2012 SP1
    Wednesday, September 4
    5:00 PM – 6:15 PM
    Meeting Room 7&8
    http://techedsessions.cloudapp.net/SessionDetail.aspx?id=2287

  • Creating Lab Computer Objects

    So I’m getting my preparation done for TechEd 2013 on the Gold Coast and needed to fill my ConfigMgr hierarchy with some dummy computer objects. My session being PowerShell for ConfigMgr 2012 SP1, of course I went straight to PowerShell to do the work for me. 

    I’m not looking for anything too special; 1000 laptops, 1000 desktops and 500 servers for my demo domain contoso.com.

    ConfigMgr can be a little picky when it comes to AD System Discovery, such as requiring a matching DNS record and a valid Operating System value. All of the options below are required otherwise you get errors in the ADSysDis.log.

     

    Here’s my script (note: you must have the Active Directory PowerShell module installed on the local machine)

     

    Import-Module ActiveDirectory
    $Count=1
    $LaptopCount = 1001
    $DesktopCount = 1001
    $ServerCount = 501
    # Create Laptops
    While ($Count -lt $LaptopCount)
    {
    New-ADComputer -Name "CON-LAP-$Count" -DNSHostName "CON-LAP-$Count.contoso.com" -OperatingSystem "Windows 7 Enterprise" -OperatingSystemVersion "6.1 (7600)"
    Add-DnsServerResourceRecord -ZoneName contoso.com -Name "CON-LAP-$Count" -IPv4Address "192.168.169.123" -A
    $Count = $Count + 1
    }
    $Count = 1
    # Create Desktops
    While ($Count -lt $DesktopCount)
    {
    New-ADComputer -Name "CON-DSK-$Count" -DNSHostName "CON-DSK-$Count.contoso.com" -OperatingSystem "Windows 7 Enterprise" -OperatingSystemVersion "6.1 (7600)"
    Add-DnsServerResourceRecord -ZoneName contoso.com -Name "CON-DSK-$Count" -IPv4Address "192.168.169.123" -A
    $Count = $Count + 1
    }
    $Count = 1
    # Create Servers
    While ($Count -lt $ServerCount)
    {
    New-ADComputer -Name "CON-SVR-$Count" -DNSHostName "CON-SVR-$Count.contoso.com" -OperatingSystem "Windows Server 2012 Enterprise" -OperatingSystemVersion "6.2 (9200)"
    Add-DnsServerResourceRecord -ZoneName contoso.com -Name "CON-SVR-$Count" -IPv4Address "192.168.169.123" -A
    $Count = $Count + 1
    }

    Active Directory Computer accounts

    image

    DNS A Records

    image

    Matt Shadbolt