Consider the following scenario. You install SCCM 2007 with SP2 console on Windows 7 machine and you face issue when you run the console unable to connect to the SCCM site server by using a remote SMS Administrator console.

Additionally the following error logged in Adminui.log file:

Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nThe ConfigMgr Administrator console could not connect to the ConfigMgr site database. Verify your user has read permissions to the ConfigMgr site and then try to connect again.

\r\n at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectio ManagerInstance(String connectionManagerInstance)

at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.BuildTreeWorker()\r\nAccess is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))

\r\nSystem.UnauthorizedAccessException\r\nAccess is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))\r\n at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

Cause:

User who tried to use remote connection with SCCM administrator console not member of local group named Distributed COM.

RESOLUTION:

To resolve this issue add the user who try to make remote connection to SCCM administrator console to the Distributed COM Users local group.

Abduljalil Abolzahab

SC Configuration Manager/Windows 7 Deployment

Prepare the Windows Environment for Configuration Manager

To allow ConfigMgr clients to query Active Directory Domain Service to locate site resources, three actions are required:

1. Extend the Active Directory schema.
   
2. Create the System Management container.
   
3. Set security permissions on the System Management container.
   

Extend the Active Directory Schema

To extend the schema user account must be member of the Schema Admins Group or who has been delegated with required permissions to modify the schema.

You can extend the Active Directory schema by running the extadsch.exe file located in the SMSSETUP\BIN\X64

Create the System Management Container

Configuration Manager does not automatically create the System Management container in Active Directory Domain Services when the schema is extended. The container must be created one time for each domain that includes a Configuration Manager primary site server or secondary site server that publishes site information to Active Directory Domain Services.

You can grant the site servers computer account Full Control permission to the System container in Active Directory Domain Services, which results in the site server automatically creating the System Management container when site information is first published to Active Directory Domain Services. However, it is more secure to manually create the System Management container.

In this document we are going to grand full control permission to the System container in Active Directory Domain Service.

To manually create the system Management container please check the following link:

http://technet.microsoft.com/en-us/library/gg712264.aspx#BKMK_CreateSMContainer

Remote Differential Compression

1. On the Windows Server 2008 or Windows Server 2008 R2 computer, navigate to Start / All Programs / Administrative Tools / Server Manager to start Server Manager. In Server Manager, select the Features node and click Add Features to start the Add Features Wizard.
   
2. On the Select Features page, select Remote Differential Compression, and then click next.

   
   

3. Complete the wizard and close Server Manager to complete the configuration.

Internet Information Services (IIS)

• On the Windows Server 2008 or Windows Server 2008 R2 computer, navigate to Start / All Programs / Administrative Tools / Server Manager to start Server Manager. In Server Manager, select the Features node and click Add Features to start the Add Features Wizard.
  
• On the Select Features page of the Add Features Wizard, install any additional features that are required to support the site system roles you install on this computer. For example, to add BITS Server Extensions:

For Windows Server 2008, select the BITS Server Extensions check box. For Windows Server 2008 R2, select the Background Intelligent Transfer Services (BITS) check box. When prompted, click Add Required Role Services to add the dependent components, including the Web Server (IIS) role, and then click Next.

• On the Web Server (IIS) page of the Add Features Wizard, click Next.
  
• On the Select Role Services page of the Add Features Wizard install any additional role services that are required to support the site system roles you install on this computer. For example, to add ASP.NET and Windows Authentication:
  
• For Application Development, select the ASP.NET check box and, when prompted, click Add Required Role Services to add the dependent components.
  
• For Security, select the Windows Authentication check box.
  

  

• In the Management Tools node, for IIS 6 Management Compatibility, ensure that both the IIS 6 Metabase Compatibility and IIS 6 WMI Compatibility check boxes are selected, and then click Next.
• On the Confirmation page, click Install, complete the wizard, and close Server Manager to complete the configuration

Request Filtering for IIS

By default, IIS blocks several file extensions and folder locations from access by HTTP or HTTPS communication. If your package source files contain extensions that are blocked in IIS, you must configure the requestFiltering section in the applicationHost.config file on distribution point computers.

The following file extensions are used by Configuration Manager for packages and applications. Allow the following file extensions on distribution points:

• .PCK
  
• .PKG
  
• .STA
  
• .TAR
  

When you use the default IIS configuration on a distribution point, clients that use BITS fail to download this software deployment from the distribution point. In this scenario, the clients indicate that they are waiting for content. To enable the clients to download this content by using BITS, on each applicable distribution point, edit the requestFiltering section of the applicationHost.config file to allow access to the files and folders in the software deployment.

Install Sites and Create a Hierarchy for Configuration Manager

Setup Downloader

Configuration Manager Setup Downloader is a stand-alone application that verifies and downloads required prerequisite redistributables, language packs, and the latest product updates for Setup.

• On a computer that has Internet access, open Windows Explorer, and browse to <ConfigMgrSourceFiles>\SMSSETUP\BIN\X64.
  
• Double-click setupdl.exe. The Setup Downloader opens.
  

  

• Specify the path for the folder that will host the updated installation files, and then click Download.
  

  
  

Prerequisite Checker

The Prerequisite Checker (prereqchk.exe) is a standalone application that verifies server readiness for a site server or specific site system roles. Before site installation, Setup runs the Prerequisite Checker.

System Center 2012 Configuration Manager Setup Wizard

When you run Setup, the local computer is scanned for an existing site server and provides only the options that are applicable, based on the scan results. The System Center 2012 Configuration Manager Setup Wizard provides the following options to install, upgrade, or uninstall a site:

• Install a Configuration Manager primary site server: When you choose to install a new primary site, you can manually configure the site settings in the wizard or allow Setup to configure the site with a default installation path, to use a local installation of SQL Server with the default instance for the site database, to install a management point on the site server, and install a distribution point on the site server.
  
• Install a Configuration Manager central administration site: The central administration site is used for reporting and to coordinate communication between primary sites in the hierarchy. There is only one central administration site in a System Center 2012 Configuration Manager hierarchy and the central administration site must be the first site installed. .
  
• Upgrade an existing Configuration Manager installation: Choose this option to upgrade an existing version of System Center 2012 Configuration Manager.
  
• Uninstall a Configuration Manager site server: When an existing site is detected on the local computer, you have the option to uninstall the site server.

To install a stand-alone primary site:

• On the server where you want to install ConfigMgr 2012, open Windows Explorer and browse to <ConfigMgrSourceFiles>\SMSSETUP\BIN\X64.
  
• Double click on setup.exe, The ConfigMgr setup wizard will open.

• On the Getting Started page select Install a Configuration Manager primary site and click next.

• On the Microsoft Software License Terms accept license terms and click next.
  

• On the Updated Prerequisites Components choose Use previously downloaded updates from the following location, and set the path of updates that you download when you run setupdl.exe.
  

• On the Server Language Selection accept the default setting and click next.
  

• On the Client Language Selection accept the default setting and click next.
  

• On the Site and Installation Settings Enter your Site code, Site name and Installation folder path, plus specify if you want to Install the Configuration Manager Console.
  

• On the Primary Site Installation, You have two options:

1. Join the Primary site to an existing hierarchy.
2. Install the Primary site as a stand-alone site.

In my scenario I’m going to install Stand-alone site.

If you choose to install Stand-alone Primary site, you will not be able to join this primary site to a hierarchy after this site installation, click Yes to continue.

• On the Database Information, on Server name write database server name (In my scenario SQL installed on the same server).
  

Note: Leave Instant name blank, if you choose the default instance name during SQL setup.

• On the SMS Provider Settings, Click next.

• On the Client Computer Communication Settings, select Configure the Communication method on each site system role.

• On the Site System Roles, click next.

• On the Customer Experience Improvement Program Configuration, click next.

• On the Settings Summary, click next.

• On prerequisites Check, verify if you have any error or warning and click Begin Install and wait installation until finish.

We expect that video and VoIP for Lync Online will be available during the first quarter of calendar year 2012. As soon as it becomes available, we will notify you directly with instructions on how to enable your video and VoIP functionality.

Sincerely,

Abduljalil Abolzahab

However smsts.log location is depend on what stage the task sequence running.

Below are the locations of smsts.log:

During Windows 7 Deployment:

• Before format and partitioning hard disk: X:\windows\temp\smstslog\
• After format and partitioning hard disk: X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\

After Apply OS:

• Windows available and CCM agent not installed: C:\_SMSTaskSequence\logs\smstslog\
• Windows available with CCM agent: C:\windows\system32\ccm\logs\smstslog\

Task Sequence completes:

• For x86: C:\windows\system32\ccm\logs\
• For x64: C:\windows\SysWOW64\ccm\logs\

Abduljalil Abolzahab – SC Configuration Manager/Windows 7 Deployment

Download Silverlight 5

Download Silverlight 5 Toolkit

Typically default path of user profile in Windows 7 is %SYSTEMDRIVE%\Users, but what if customer need change user profile path to another directory, "D drive for example", to do that I need to use ProfilesDirectory setting to move the user profile folder to another location during Setup, Deployment or Sysprep.

The destination path can be on a volume other than the system drive, as long as it meets the following requirements:

• It must be on an NTFS volume.
• It must not be the path of another operating system user profile folder.
• It must not contain any serviceable components.

Solution:

To create an unattend file with ProfilesDirectory setting, please check the following steps:

• Open Windows System Image Manager, which is part of WAIK (Windows Automation Installation Kit).

•  You will receive message asking you to edit an answer file without Operating System Image "Limited" or to open Windows Image, Click Yes.

• Browse Windows 7 Media / Source folder and select “Inastall_Windows7 EDITIONNAME.clg”.

• Go to Windows Image Catalog -> Components -> right click on
  Microsoft-Windows-Shell-Setup and choose “Add Settings to Pass 7
  oobeSystem”.

• Expand Microsoft-Windows-Shell-Setup and click on “FolderLocations”,
  in the settings “ProfileDirectories” write “for Example
  D:\” to redirect user profile folder to D:\ drive

•  Save answer file with unattend.xml file, the file will look like the below snapshot:

Next step in my scenario is ether to use unattend.xml file with sysprep or include it with Task Sequence id you are using Microsoft System Center Configuration Manager – Operating System Deployment feature to deploy Windows 7.

I’ll show you how to use unattend.xml file with Task Sequence:

• Copy Answer file that we create to ConfigMgr Server.
• Startup your Configuration Manager console navigates to Site DatabaseComputer Management/Software Distribution and then selects Packages in the left pane.
• Right click on packages and choose New/package a wizard will begin.
• New Package wizard will start, click next.
• For Data Source, place a check in this package contains source files and click on Set to specify the source of the ConfigMgr package, we have to select answer file that we create.
• Follow wizard with default setting to the end.
• Copy new package to distribution Point:

1. Expand answer file package that we create.
2. Right Click on Distribution Point, and choose a New Distribution Point.
3. When a new welcome to new distribution points wizard appears click next.
4. Select your ConfigMgr server from the list and click next.
5. Review the summary and click close.

• Update Distribution Point:

1. Expand answer file package that we create.
2. Right Click on Distribution Point, and choose Update Distribution Point.

• Edit Task sequence that we use to deploy Windows 7 image.

1. Configuration Manager Console navigates to Site DatabaseComputer Management/Operating System Deployment/Task Sequence and select the task sequence that you will use to deploy windows 7 image.
2. Right click on this Task Sequence and choose Edit.
3. Go to Apply Operating System Step and check User an unattended or Sysprep answer file for a custom installation.
4. Click Package Bottom and choose package that we create for answer file.
5. Click OK

Abduljalil Abolzahab

The Microsoft Assessment and Planning Toolkit (MAP) is an agentless, automated,
multi-product planning and assessment tool for quicker and easier desktop and
server migrations and upgrades.

Microsoft Assessment and Planning Toolkit 6.0 already published in 17/05/2011 and you can download from Microsoft Assessment and Planning Toolkit.

Abduljalil Abolzahab

During preparing Master Image of any Mictosoft Operating System, in the last step before capturing the image with copy profile, It’s very important to Clear Run Commands Cache in Run dialog box from start menu which are automatically cached to be used later.

Solution:

Go to registry and follow the following path:
HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Explorer/RunMRU

and in right pane you will find entries for the Most recently used command in Run box. Delete the unwanted entries or delete all.

Abduljalil Abolzahab

SC Configuration Manager/Windows 7 Deployment

Task Sequence error 0x8007000D when task sequence trying to load BOOT image, in my case it occur after “Capture User State“, and task sequence try to “Restart to Windows PE“.

Cause:

It seems like Boot image has not been copied properly to distribution point or PXE distribution point.

Error 0x8007000D Description: The data is invalid.

Solution:

1- Remove the boot image from distribution point and PXE distribution point.

2- Add Boot image again to distribution point and PXE distribution point.

3- Update distribution point.

An Operating System deployment task sequence that use USMT 4.0 – HardLink fail in Capture User State with error 0×80070714.

Cause:

The issue can occur if Original machine (Windows XP/Windows7) still with ConfigMgr 2007 client SP1, Since USMT 4.0 with HardLink feature release after ConfigMgr 2007 RTM and ConfigMgr 2007 SP1, so both RTM and SP1 clients will not work with USMT 4.0

Solution:

Upgrade ConfigMgr 2007 RTM or SP1 client to ConfigMgr 2007 SP2.

ConfigMgr 2007 version number:

• ConfigMgr RTM Version 4.00.5931.000
• ConfigMgr SP1 Version 4.00.6221.1000
• ConfigMgr SP2 Version 4.00.6487.2000

Abduljalil Abolzahab

SC Configuration Manager/Windows 7 Deployment