Disclaimer
The opinions expressed herein are my own personal opinions and do not represent anyone else's view in any way, including those of my employer.
© Copyright 2007
The opinions expressed herein are my own personal opinions and do not represent anyone else's view in any way, including those of my employer.
© Copyright 2007
First of all, Happy New Year,
and may everyone find that in 2008 that your glass is more than half full, you and your loved ones are all very healthy and overly happy, that your careers are very prosperous, and that you gain all that you desire and more.
As we welcome another year and reflect on the year ending it is always nice to note what was the highlights of the year. So below is my personal top ten of 2007 when it comes to Systems Management.
10. Thursday, October 23rd, System Center Partner Airlift. It was actually the dinner on Thursday night that got this on the list. I set dinner for about 12 people at a local steak house, Daniel’s, and it ended up that at this dinner we had sitting around the table, Jeff Gilbert, Michael Niehaus, Paul Thomsen, Garth Jones, and Greg Ramsey, amongst others. 
9. New class in SMS 2003 SP3 causes CPU’s to jump to 100% utilization, and is fixed.
8. Saturday, July 7th, SoftGrid 4.2 was available, adding support for Vista. 
7. Monday, May 7th, System Center Essentials goes RTM. This doesn’t get a lot of press either but for SMB sized companies this has great potential.
6. Monday, April 23rd, I started my new position with 1E, I did say my personal top 10 so this had to come in somewhere on the list! 
5. Friday, March 23rd, System Center Operations Manager goes RTM. While we don’t often talk much about it, it is still a great milestone.
4. Wednesday, November 14th, Microsoft Deployment was released. After Michael, Tim, and the other team members had been slaving away for months it was finally ready for all of us. 
3. Friday, April 27th, SMS 2003 SP3 was released. The AssetIntel piece makes this a very important service pack for those sticking with SMS 2003.
2. Monday, March 26th, MMS 2007 opens in San Diego, CA. This is always such a great event. The training, meeting people, product news, it can’t be beat and each year it gets better and larger.
1. On August 24th 4 PM PDT, System Center Configuration Manager goes RTM. 
Regards and Happy New Year!
The Clendenen’s
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
TechNet Webcast: Optimizing Desktop Management with System Center Configuration Manager and Microsoft SoftGrid Application Virtualization (Level 300)
Event ID: 1032358169
Language(s):
English.Product(s):
System Center.Audience(s):
IT Professionals.Duration:
60 MinutesStart Date:
Tuesday, January 15, 2008 1:00 PM Pacific Time (US & Canada)
One of the biggest challenges IT departments face in today’s organization is reducing the cost of managing their desktops. Broader demands from the business, fast-paced technology cycles, and increasing security threats place a heavy demand on IT departments to deliver higher value at a lower cost. IT teams must test for application compatibility, maintain user productivity, keep track of assets, secure the desktop, and more.
The answer to these challenges is to improve desktop optimization. Reduction of desktop complexity speeds deployments, streamlines management, and increases security. In this webcast, we discuss centralized deployment and management of desktops, laptops, and devices with Microsoft System Center Configuration Manager. When used in conjunction with the Microsoft Desktop Optimization Pack, management is extended across both physical and virtual desktops and applications resulting in the highest levels of efficiency for overall enterprise management.
Regards,
Anthony
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
Computer Active is giving away the Pro version of AVG for free. I use the free version of AVG on several computers at home and it works fine, you get those annoying widows during updates because it is free, with Pro you can turn that off. Right now it looks like their servers are being flooded but you have until Jan. 17th with the option to stop the offer at anytime, which means they only have so many licenses.
Details here.
Regards,
Anthony
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
Seasons Greetings Everyone!
Overview
The MSI Utility for Microsoft Application Virtualization is a new tool designed to extend virtual application deployment in certain key scenarios. In cases where a computer running Microsoft System Center Virtual Application Server is not available, the MSI Utility allows delivery of sequenced applications directly to Microsoft SoftGrid Application Virtualization for Desktops and Microsoft SoftGrid Application Virtualization for Terminal Services.
The MSI Utility enables the distribution of virtual applications without streaming. Instead, it uses Windows Installer to load and configure virtual applications. By leveraging this standard format, the MSI Utility achieves Microsoft Systems Management Server 2003 and Microsoft System Center Configuration Manager 2007 platform version-agnostic distribution of virtual applications if supported by organizational Electronic Software Distribution (ESD) systems. As such, the MSI Utility is a stepping stone to the richer deployment options available in Microsoft System Center Virtual Application Server 4.5.
The MSI Utility extends application deployment methods to a broad range of ESD systems, including Systems Management Server 2003 and System Center Configuration Manager, as well as other methods such as network shares, removable disks, and memory keys. By using an ESD system to deploy virtualized application packages to disconnected SoftGrid Application Virtualization Desktop Clients, users can run virtualized applications without connecting to a computer running Microsoft System Center Virtual Application Server.
Download details: MSI Utility for Microsoft Application Virtualization
Regards,
Anthony
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
This is a whole list of Systems Management WebCasts that go back as far as 2000 with some SMS 2.0 stuff, here is some newer SMS 2003 
WebCasts, and here is a search string for ConfigMgr WebCasts, I couldn’t find a page that just listed all of them.
Past Support WebCasts
Regards,
Anthony
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
Back at the end of September I was preparing my home lab for ConfigMgr testing. Since then I have been trying to get back to this article to proof it and tidy it up for publishing. After a number of requests and a light amount of work after 15 hour day today I am sitting in my hotel room, eating mediocre room service, while the Bears are beating the Vikings on MNF, so what better time to do it.
Here are the basic software prerequisites for upgrading from SMS 2003 to ConfigMgr:
Other considerations prior to upgrading:
You must have your SMS 2003 site in Advanced Security mode. This is the only mode in ConfigMgr.
No support for legacy clients. All clients must be advanced clients prior to the upgrade or they will no longer be clients.
Remove any 2003 Feature packs such as, OSD, Mobile Device Management, DCM, etc.
The 2003 version of ITMU is not supported in ConfigMgr so you must upgrade it right after completing the upgrade.
BUT – When I did my upgrade I left ITMU installed and it upgraded my server during the install.
Disable SQL replication prior to upgrading.
If you have modified the criterion of any of the default collections (maybe reports too), create new collections with different names (make use of linking) prior to the upgrade as these will be replaced with the defaults during the upgrade.
Prerequisites for different site roles:
Management Point – IIS 6.0, with BITS 2.0 and WebDAV extensions
Distribution Point if BITS enabled – IIS 6.0, BITS and WebDAV
Distribution Point if not BITS enabled – none
Reporting Point – IIS 6.0 and ASP
Server Locator Point – IIS 6.0
Software Update Point – IIS 6.0, WSUS 3.0 and BITS 2.5
Remote SUP – WSUS Admin console must be installed if a site is using WSUS server on another site.
Each SUP only supports 25,000 clients, if you have more than 25,000 clients assigned to a single site NLB clustering must be used (more info here).
Clients – WUA 3.0 and Windows Installer 3.1 (for updates)
Backing up your SQL (2000) db’s
Before we begin to upgrade to ConfigMgr we have to first upgrade to SQL 2005, if you are already at SQL 2005 then you can obviously skip this step but you will need to make sure you backup your db’s in SQL 2005 before you upgrade to ConfigMgr and that is covered later.
Since I am running several of the 1E tools in my lab I have the Agility Framework db to also backup, you may only need to follow these steps for your SMS db but the steps are exactly the same.
Backup Agility Framework db
Note: Before you start the backup if you are going to backup to disk like I am through Explorer create a folder to store your backups in as the wizard does not have a New Folder button to create a folder on the fly
In SQL Ent. Mgr. expand the databases, right click on the db you wish to backup, from the context menu choose All Tasks and then backup db.
This starts the Backup wizard, you can modify the name if you choose but by default it will append the db name with "backup." Also when you enter the name in the next couple of steps it will override this so don’t waste your time unless there is some company procedure you have to follow here.
Under Destination click the Add button and browse to the folder you want to store your backups in.
The name that you enter here will be the file name for you backup and will override the text you entered in the first window.
After you choose the destination and file name click OK and you will return to the SQL Server Backup window. You can leave all other choice at their defaults and start the backup by clicking the OK button. Depending on the size of your db this could take just a few seconds or a couple of minutes, when it finishes the backup you will be greeted with a popup window telling you it complete successfully like below. You can exit SQL Ent. Mgr. at this point.
Upgrade SQL 2000 to 2005 with SP2
Stop SQL server
SQL 2005 preqs: Install SQL Native Client and Setup Support Files
Complete configuration check
Select the components to install – SQL Server Database Services and Workstation components.
You are likely using a default instance so no need to choose a named instance unless you have your SQL db configured as such.
Specify the account you use to start your SQL instance, this should match what you are currently using for SQL 2000.
The setup process should not take too long but don’t forget to install SP2 for SQL. (download it here).
Prior to the upgrade it will check to see if all the SQL services are stopped and will not let you proceed until they are, fortunately it will check and let you know what needs to be stopped, including the PID if you need to go that deep.
After all services are stopped the install will proceed.
At this point I think the server had earned a reboot, even though it has not been requested.
After the reboot if you so choose, now is the time to remove the installed feature packs.
Extend AD Schema
Extending the schema is not something you should take likely but since you are doing all this in your lab it is not such a big deal. But you should be following your upgrade plan that you formed prior to testing it. Schema extensions cannot be reversed and are domain wide, you need to understand what impact they will have on your domain so plan carefully for these before you decide to implement them.
Some drawbacks to not extending the schema are:
Roaming is limited, clients will not request data from a local MP and will revert to their assigned MP instead.
NAP will not work or Native mode
Clients will not be able to auto assign themselves unless the SLP has been published to WINS and the MP has been added to DNS manually, alternately if the SLP from 2003 has been added to AD domain services then clients can auto assign. So in the upgrade scenario this is very likely to be true.
If you use secure key exchange between sites and are upgrading then you should not have any problems - I think. But you cannot use secure key exchange if you want to implement this after the upgrade without the schema extensions.
Dynamic updates to ports for client server communication will not occur.
Most of these have workarounds like passing cmd line parameters during client install to assign the clients manually, but a couple of them do not. You can get more details on workarounds and potential impact on the ConfigMgr TechNet site here.
If you are going to implement the extensions this is done the same way as previous schema extensions. The logged on account must have schema extension rights, this is not part of the typical domain admin rights, it is a separate group. Once you are logged in with the appropriate rights you can just open up a command prompt window, and from the ConfigMgr CD in the SMSSETUP\BIN\I386 directory locate the file extadsch.exe. Drag it to the command prompt window and make sure it has focus and then hit the Enter key. Once your blinking cursor returns, in the root of the boot drive you should find a log file named ExtADSch.log, open that up and look for "Successfully extended the Active Directory schema." down towards the end of the file, if you see this line all went well, if not, scroll up…
According to my log there are four new attributes that are added:
Cn=mS-SMS-Health-State
Cn=mS-SMS-Source-Forest
Cn=mS-SMS-Version
Cn=mS-SMS-Capabilities
And four classes are updated:
LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=arz,DC=local
CN=Schema,CN=Configuration,DC=arz,DC=local.
LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=arz,DC=local.
LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=arz,DC=local.
For clarities sake my lab my domain is ARZ.local
Test db upgrade on backup created earlier
Remember the db backups we made, we don’t need those anymore we are at SQL 2005 now, but keep them just in case. Just like all the SMS 2003 service pack upgrades we need to test our SMS db prior to installing. Considering the time it takes to do this it is well worth testing the db, assuming you have the SMS 2003 Recovery Expert installed and you have tested it, how long has it been since you tested it? You do have it installed right? Microsoft has a couple of variations on this process that you may like better, they can be found here, my methods are the same as I have used in the past with customers, in my previous articles and when I was an SMS engineer so I prefer them not that any are really and better or worse.
If you are new to SQL 2005 what you used to do in Enterprise Manager you now do in SQL Server Management Studio. Find this shortcut on your Start menu and then connect to the local SQL instance (assuming you are running your db locally). We are going to create a new test db and restore it from our backup to test against it.
Expand the databases folder, right click it and select New Database.
You should see the New Database window like the image above, in the name field type in SMS_test and then click the OK button.
Now you should be back in the SQL Studio window and select your test db, right click on it, then select Tasks, Restore, Database like so.
You should see the Restore Database wizard now, select your test db in the Destination to restore – To database drop down menu, and from the Source for restore select From database and make sure you SMS db is the source.
On the left hand side you will see General and Options, select Options.
Check the top box Overwrite the existing database, and now we need to tell it where to store our LDF and MDF files, by default it should have the source files, which we do not want to overwrite, actually you can’t do this without getting an error.
Just click the ellipse buttons to specify new destination paths and names for the MDF and LDF files.
Before
After
Check your paths one more time like a good admin and then click OK to start the restore.
Just as with most SMS tasks, this will take a few minutes. And when you are finished you should see this.
Now we can do a test upgrade of our SMS db without risking any real damage. Click OK and close SQL Studio.
I found that I had to remove SQL 2000 completely before the following test would run, even though I specified the new SQL 2005 test db name the check would return and tell me I needed to install SQL 2005 SP2 in order to run setup. This also required a reboot, I guess I should have saved mine from earlier.
This all led to a very interesting development, it seems that during my uninstall of SQL 2000, it removed both 2000 and 2005.
As you can see I no longer have SQL 2000 in Add or Remove Programs, SQL 2005 is still listed but
See what happens when I click on Change.
The only options are to modify SQL Reporting Services or Workstation components…
I installed SQL 2005 again, installing just the database portion, it installed to a sub directory.
I will save you all the gory details but I was able to just attach the db from the SMSDATA folder. If this is intended during the uninstall this needs to be documented better, if it is not intentional then I would say this might be a BUG in the uninstaller, but maybe it was just me…
On the ConfigMgr CD in the folder SMSSETUP\BIN\I386 drag setup.exe to an open command prompt window and add the /testdbupgrade switch and then type the name of the backup db so it looks like this.
When it’s done you should see this.
Run ConfigMgr prerequisite check
Upgrade
You can begin the upgrade to ConfigMgr by double clicking the setup.exe in the I386 directory on the CD. After the initial welcome screen telling you what you need to complete prior to running setup you should see the setup options page where you will have the choice to upgrade or uninstall ConfigMgr, we obviously want to upgrade and that should be selected so click Next.
On the license agreement page review the license agreement and then check the box accepting it and then click Next again.
You can decide to participate in the customer feedback program or not on the next screen and after you have made your choice click Next again.
On the next screen the product key is entered, this will likely be filled in for you already, click Next.
The next screen gives you the option to allow setup check for any missing updates and download them for you, or you can bypass this and point it at a path where you have already stored the updates. After your choice click Next to proceed.
The next screen will ask you where you want to store the files if you chose to let setup download the files automatically, I would image this screen is the same for either method based on the wording.
Don’t forget to set your proxy settings in IE to auto detect if you are not using the latest fixed version of eval. I am using a different version supplied to 1E so it still has the bug in it but after making the change in IE it happily started downloading 88 files…
After the downloads have finished you should be presented with a summary page, check to make sure you have the selections you desire and then click Next.
This is where the database upgrade will take place and a final prerequisite check happens. Any errors or warnings listed may prevent the install or just provide information and allow the install to proceed. When you feel that you are ready and the prerequisite checks have passed, click the Begin Install button to launch the install!
And now the fun begins – this is what you should be seeing…
During this process you should see the ITMU upgrade wizard appear, this is new for the RTM version as I don’t recall it in the betas I used.
Click Next and the next screen will ask you if you want to download the cab file for the updates or use a locally stored version. Make your appropriate selection and click Next. I will allow it to download, you should only be using the local version if you are running your site server without a connection to the Internet.
Just a short time later you should see the finish dialog.
Click finish to allow the setup of ConfigMgr to proceed.
And we have lift off…
One final screen remains, you can view the install log, launch ConfigMgr, or just end the install.
To verify that the site has completed the install successfully at a minimum you should review the ComponentSetup.log in the root of C, the configMgrSetup.log, also located in the root.
If you want to patch using ConfigMgr you will need to download and install WSUS. After you kick off the install do not waste any time trying to sync or configuring WSUS we do this all through the ConfigMgr console.
Select the custom site install to get the alternate ports if you are installing the WSUS server on your ConfigMgr server, as port 80 is already in use.
You should install the full version on the site server or server that you plan to use as your Software Update Point, the admin console only needs to be installed on site servers that will deploy patches but not download the patches directly.
I will tell it store updates locally on my server, make sure you choose a drive with adequate space as you can download more than your average monthly patch Tuesday patches with this, it is a WSUS server.
Skip this…
Now let’s start using ConfigMgr…launch it from your Start ==> All Programs –> Microsoft System Center -> Configuration Manager 2007
First view of the console….
Expand Site Settings and go to Site Systems and either right click your server name and choose
New Roles or highlight it and use the menu on the right panel to choose the same. Fill in the FQDN.
So let’s start by configuring the boundaries. This is under Site Settings, it has its own folder now instead of going to the site properties.
It should have carried over your settings from the previous install so just verify that these settings are here and correct.
Select the roles you want to add, at minimum choose Software Update Point and then click Next.
Let’s move on to configuring the WSUS/SUP and finish this article up.
Move down to Component Configuration still below Site Settings and in display window in the middle of the console select Software Update Point Component, right click on it and select Properties.
Welcome to task sequences…
If you have a proxy between your server and MU then you should enter those settings here. Keep in mind that the settings you enter here will override any settings you have entered into WSUS but if you followed my install you should have cancelled the settings wizard after the WSUS setup.
Make sure you check this box, you can guess what will happen if you don’t… 
These ports should be the same that you configured during the WSUS setup, by default it will use http and SSL ports, you can modify these if you need to but they must match the settings in IIS.
Click Next to continue.
On the next screen you will have to tell your SUP to either sync with a local WSUS server or MU directly, you can also choose to not sync if you are using a manual sync method. You can also decide if you want clients to report on WSUS events, this has nothing to do with ConfigMgr reports it is only used for WSUS and will not feed any info into ConfigMgr.
Click Next to continue to the sync schedule screen, you can set the SUP/WSUS server to sync on a custom schedule or simple, just like you would schedule the ITMU sync ad in 2003. I would have mine run every Saturday and the evening of Patch Tuesday. Define your schedule and lets move on to Classifications, click Next when you are done.
Remember my warning about lots of disk space, well here is the list of different types of updates, choose what class of updates you want to pull down and then click Next to decide what products you want to pull down those types of updates for and then click Next again and decide what languages you want to download them in.
After that you should see the Summary screen, review the settings you have made and if you need to go back and make any changes, once you click Next it is going to make the changes you have specified.
And after a short period you should see this…or something similar
And now if you go up to Site Settings, Component Configuration and double click the Software Update Point Component your screen should look like this.
You now have a working site with the ability to deploy patches, once you upgrade your clients that is, but that will have to be another article.
Any questions, corrections, so on, let me know.
Regards,
Anthony
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
If you wonder how I make those images, its all done with Paint .NET, which is 100% free and all the plugins are 100% free. I know Ron and Rod use it as 
well and you cannot be the price. I have used Photoshop and it is a great product but kind of pricey! Paint .NET is build from the .NET Framework and costs you nothing so if you haven’t tried it and use another similar product you should give it a try.
Regards,
Anthony
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
There is a hotfix available for an issue where in ConfigMgr the status summarizer stops working and a backlog SVF files begin to pile up in the OfferSum inbox. This was first reported publicly on December 3rd on the myITforum.com SMS mailing list by Lane K. Shortly after it was reported Brian Huneycutt, an Escalation Engineer at Microsoft, launched an investigation into this issue. After it was confirmed a KB was created and sent through the release process.
Update: (Dec 9 9:00 GMT) hotfix now publicly available for download here.
Currently (Dec. 8th 1200 GMT) the KB is available by contact PSS, your TAM, or standard Microsoft Support (1-800-936-4900) and referencing KB 945898. It is also available on the premier.microsoft.com site if you have a Premier Support contract. Rick Jones at AT&T Wireless (formerly Cingular Wireless) reported that when he contacted Microsoft Support that he was told no such KB existed, if this happens to you just ask to speak to an engineer and they will be able to get the hotfix mailed to you.
Additional details on the fix:
The back log of files should start processing almost immediately after you apply the fix and can be monitored in the OfferSum.log (see note above).
This issue could have other side effects that may not make it immediately apparent as to what is causing the issue you are seeing.
I would very strongly advise against EVER modify the site control file for ANY reason. I have seen at least one email where the admin deleted lines from the site control file to resolve this issue. If this file becomes corrupt or is modified in certain ways it could cause far more serious issues than a backlog of files in your Inbox. As Microsoft puts it “because it is possible to irreparably damage your SMS site.” If you need to make changes to the site control file do it programmatically through the exposed WMI classes and the SMS Provider.
Regards,
Anthony
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
In ConfigMgr there is a new feature that hasn’t gotten much attention called Maintenance Windows. This is a feature that I have heard numerous requests for and it gets a bit closer to the infamous ‘Big Red Button’.
So what is a maintenance window? A maintenance window is a rule applied to a collection of ConfigMgr clients that prevents those clients from:
Except during the time defined in the maintenance window. All other client actions still occur as scheduled such as policy refresh, inventory, package downloads, and DCM evaluation.
Sounds simple enough right? So what else is there to consider? The first question that is likely to come to mind is…
If maintenance windows are applied to collections does that mean that the maintenance window rules only apply to advertisements that target that same collection? Allowing the client systems to run other advertisements if they are in other collections.
Answer – No, the client will NOT run ANY of the above unless it is within the maintenance window(s) no matter what collection the advertisement is targeting. But, there are two options for each 
advertisement that you can use to override these settings. These options are on the Schedule tab of each advertisement in ConfigMgr and will allow you to ignore the maintenance window to run the program and ignore the maintenance window when a reboot is required.
Note: There are similar overrides for OS Deployments and Update Deployment packages as well.
These are checkboxes so you can choose one or both options, allowing you to install during a non-maintenance window period but prevent the reboot, or to allow both to happen outside of the specified maintenance window. It is of course possible to have multiple maintenance windows applied to a client if you have the client in more than one collection where maintenance windows are applied, but maintenance windows do not apply to subcollections.
There are some things to watch for when you create a program that will be run by clients with maintenance windows applied to them. First, the maximum
runtime for 
the program, this setting is what ConfigMgr (and SMS 2003) uses to decide when to quit monitoring a running program and move on, often times this would be left to Unknown when you create a package and program manually, instead of pointing it at a definition file, if a ConfigMgr client that has any maintenance windows applied to it and it gets a program with the estimated run time set to Unknown the program will run as long as there is enough minutes left for the countdown to complete before the maintenance window closes. Even though the value of Unknown equates to 12 hours when monitoring a programs runtime, this is evaluated as 0 when determining if a program can run within a maintenance window. This is because before the ConfigMgr client agent will allow a program to run it must be able to calculate the time it will take the program to run plus the countdown timer and subtract that time from the amount of time left in the maintenance window. If the estimated runtime is n, and the countdown is c, and the minutes left in the maintenance windows is m, we get n + c <= m OR if n + c > m then the program might not have enough time to run before the maintenance window expires and it isn’t allowed to run, and if n is unknown or 0 then it is really evaluated as 0 + c <= m and so the program will run on the client as long as it has enough minutes left to complete the countdown.
It is also important to understand that a client can be in any number of collections, and any or all of those collections can have one or more maintenance windows applied to its clients. Because of this, designing of your maintenance windows and building new collections for those maintenance windows is a very good idea. You should also devise a standard type of naming convention for the maintenance windows collections, Microsoft suggests something like MW-<collection name>, just make sure you do follow some sort of standard when naming the collections. If you need to figure out what maintenance widows a particular client has applied to it there is a ConfigMgr report that will tell you exactly that “Maintenance Windows Available to a Particular Client”.
Some additional details about Maintenance Windows:
If you want to experiment with maintenance windows you can follow these steps to create one or more:
Notice the checkbox for setting this to only apply to OSD.
To watch the magic on the client side, navigate to \\clientComputer\admin$\system32\ccm\logs\execmgr.log
And then create a mandatory ad to run prior to the maintenance window being open and you should see the execution of the program being blocked.
Relevant Links:
How To Set A Maintenance Window
Program Run Scenario using Maintenance Windows
Regards,
Anthony
Anthony Clendenen | Solutions Engineer | 1E
© 2007 Anthony Clendenen
More Options ...
Categories
Tag Cloud
Blog RSS
Comments RSS
Void 
Life « Default
Earth 
Wind 
Water 
Fire Light 
Last 50 Posts 
Back
