Browse by Tags

Setting DNS Search Order with ConfigMgr

If you are trying to set the DNS Search order during an OSD task sequence, this will never work if you specify a 127.0.0.1 address. It seems like both WMIC and ConfigMgr fails to use this as a valid address. Please also note that the DNS step has to be configured if you are setting a static IP, it cannot...

Posted to 1E Blog (Weblog) by Anonymous on 05-14-2009
Filed under: System Center, OS Deployment
Running a ConfigMgr Task Sequence command line as a specified user

When you use the "Run this step as the following account" in ConfigMgr you need to be aware of the fact that the OSD environment does NOT follow to the new user environment. This means that scripts referencing the Microsoft.SMS.TSEnvironment or the BDD/MDT oEnvironment.Item objects will fail...

Posted to 1E Blog (Weblog) by Anonymous on 05-18-2009
Filed under: System Center, OS Deployment
Importing and Exporting ConfigMgr Tasks Sequences

First of all, if you want to programmatically import/export tasks sequences ensure that you are on SP1, that contains the undocumented import functionality. More about that in later posts. If you want to import a task sequence, ensure that you have all the ConfigMgr tasks sequence extensions as you did...

Posted to 1E Blog (Weblog) by Anonymous on 05-21-2009
Filed under: System Center, OS Deployment
Running a tasks that stops WMI as a part of a ConfigMgr task sequence

If you want to run a certain application or configuration that stops either WMI or the Agent Host you have to run it as a "Run Command Line" step. All "Install Software" steps is executed by the execmgr by the Agent Host, and when the application stops either WMI or the Agent Host...

Posted to 1E Blog (Weblog) by Anonymous on 05-26-2009
Filed under: System Center, OS Deployment
ConfigMgr package programs cannot use task sequence variables!

When running a normal ConfigMgr package/program as a step in a task sequence, you cannot use variables on the command line. This happens because the execution of the program is actually managed by the execmgr, the clients normal execution manager, which does not know of any of the OSD environment. There...

Posted to 1E Blog (Weblog) by Anonymous on 05-26-2009
Filed under: System Center, OS Deployment
Problem encountered creating MDT 2008 Boot Image when SMS Provider is not installed on site server

Let me first state that this is not necessarily a problem with MDT 2008 or ConfigMgr, but has to do with setting share-level permissions. So who should be responsible for doing that? The product (automated), or the admin (manually)? So let’s walk through creating the problem and how to resolve...

Posted to 1E Blog (Weblog) by Anonymous on 07-08-2009
Filed under: System Center, 1E Internal blogs, OS Deployment
MDT 2008: Error occurred integrating with ConfigMgr

After installing MDT 2008, you can then integrate it with ConfigMgr by running the Configure ConfigMgr Integration wizard. In doing this, I uncovered an issue where if the ConfigMgr SMS Provider is NOT installed on the site server, the wizard will error-out. A hint to the root cause of the problem...

Posted to 1E Blog (Weblog) by Anonymous on 07-08-2009
Filed under: System Center, 1E Internal blogs, OS Deployment
Problem encountered creating MDT 2008 Boot Image when SMS Provider is not installed on site server

Let me first state that this is not necessarily a problem with MDT 2008 or ConfigMgr, but has to do with setting share-level permissions. So who should be responsible for doing that? The product (automated), or the admin (manually)? So let’s walk through creating the problem and how to resolve...

Posted to 1E Blog (Weblog) by Anonymous on 07-08-2009
Filed under: System Center, 1E Internal blogs, OS Deployment
MDT 2008: Error occurred integrating with ConfigMgr

After installing MDT 2008, you can then integrate it with ConfigMgr by running the Configure ConfigMgr Integration wizard. In doing this, I uncovered an issue where if the ConfigMgr SMS Provider is NOT installed on the site server, the wizard will error-out. A hint to the root cause of the problem...

Posted to 1E Blog (Weblog) by Anonymous on 07-08-2009
Filed under: System Center, 1E Internal blogs, OS Deployment
ConfigMgr package programs cannot use task sequence variables!

When running a normal ConfigMgr package/program as a step in a task sequence, you cannot use variables on the command line. This happens because the execution of the program is actually managed by the execmgr, the clients normal execution manager, which does not know of any of the OSD environment. There...

Posted to 1E Blog (Weblog) by Anonymous on 05-26-2009
Filed under: System Center, OS Deployment

Page 1 of 3 (21 items) 1 2 3 Next >