Browse by Tags

• 1E Internal blogs
• 1E News
• 1E Products
• ConfigMgr
• Events
• Green IT
• IT Efficiency
• NightWatchman
• Nomad
• R3
• Server Power Management
• Shopping
• Windows 7

• Windows 7 Deployments Made Easy with 1E

  Brad and Sumir discuss the benefits of using Configuration Manager in deploying Windows 7, and then go on to talk about the value-add of 1E’s solution and product portfolio, in particular Nomad, PXE Lite, and the professional services they offer... Posted Nov 09 2010, 09:13 AM by 1E Blogs Filed under: System Center, OS Deployment, 1E News, Windows 7, ConfigMgr

• 1E Presentations and Demonstrations Schedule for TechEd Europe 2010

  As you’re sifting through the Cloud this week at TechEd 2010, you’ll want to stop by the 1E booth for a breather and to hear some valuable information to take back to the job with you. Here’s our stand (Stand … Continue reading → Read More... Posted Nov 08 2010, 07:36 AM by 1E Blogs Filed under: System Center, OS Deployment, 1E Products, 1E News, Green IT, Windows 7, Server Power Management, ConfigMgr, Shopping, IT Efficiency, Events, NightWatchman, R3, Nomad

• ConfigMgr OSD: Always including certain files in your Boot Images -think Trace32

  How many times have you needed to use Trace32 to troubleshoot an OSD deployment especially when running under WinPE? Sometimes you could just map a network drive to a share and run it but maybe the network drivers didn’t get included or that just... Posted Jul 17 2010, 04:34 PM by 1E Blogs Filed under: System Center, OS Deployment, Windows 7, ConfigMgr

• 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... Posted Jul 08 2009, 01:16 PM by 1E Blogs 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... Posted Jul 08 2009, 11:01 AM by 1E Blogs 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... Posted May 26 2009, 11:45 AM by 1E Blogs 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... Posted May 26 2009, 04:11 AM by 1E Blogs 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... Posted May 21 2009, 10:30 AM by 1E Blogs 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... Posted May 18 2009, 09:37 AM by 1E Blogs Filed under: System Center, OS Deployment

• 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... Posted May 14 2009, 05:27 AM by 1E Blogs Filed under: System Center, OS Deployment