Archive for September, 2009

How to: Prepare Windows 2008 Server for installing SCCM 2007

When you want to install Microsoft System Center Configuration Manager 2007 on a Windows 2008 Server, you have to install some prerequisites before you can begin to install.

1.) Install the following Role: Webserver IIS
2.) Install the following Role Services of Webserver IIS
     – Web Server
          – Common HTTP Features
          – Static Content
          – Default Document
          – Directory Browsing
          - HTTP Errors
          – HTTP Redirection
     – Application Development
          – ASP.NET
          – .NET Extensibility
          – ASP
          – ISAPI Extensions
          – ISAPI Filters
     – Health and Diagnostics
          – HTTP logging
          – Logging tools
          – Request Monitor
          – Tracing
     – Security
          – Basic Authentication
          – Windows Authentication
          – URL Authorization
          – Request Filtering
          – IP and Domain Restrictions
     – Performance
          – Static Content Compression
     – Management Tools
          – IIS Management Console
          – IIS Management Scripts and Tools
          – Management Service
          – IIS 6 Management Compatibilty
          – IIS 6 Metabase Compatibility
          – IIS 6 WMI Compatibility
          – IIS 6 Scripting Tools
          – IIS 6 Management Console
3.) Enable the following feature, BITS Server Extensions
4.) Enable the following feature, Remote Differential Compression
5.) Open the IIS Manager
6.) Open the WebDAV Authoring Rules
7.) Make a new Authoring Rule with:
     – Allow access to: All content
    
- Allow access to this content to: All users
    
- Permissions: Read
8.) Open the WebDAV Settings and edit the following options:
     – Allow Anonymous Property Queries: True
     – Allow Custom Properties: False
     – Allow Property Queries with Infinite Depth: True
     – Allow Hidden Files to be Listed: True
9.) Apply theses settings
10.) If you need to extend the Active Directory Schema, you’ve to use the LDIFDE tool. You need to install the Remote Server Administration Tools (RSAT):
     – ServerManagerCmd -i RSAT-ADDS
11.) After the prerequisites check you can report the following logfile:
     – C:\ConfigMgrPrereq.log
     – C:\ConfigMgrSetup.log

SCCM_2008_01    SCCM_2008_02    SCCM_2008_03

SCCM_2008_04    SCCM_2008_05    SCCM_2008_06
 

SCCM 2007 Active Directory System Discovery

Discovery is a Microsoft System Center Configuration Manager 2007 process that allows Configuration Manager 2007 to search various places on your network for computers that can be managed as Configuration Manager 2007 clients. Discovery can also locate resources that cannot be clients, such as printers and routers. By default, all the discovery methods are disabled, exept one, the Heartbeat Discovery. We come back on this item later on.

In this example i’m going to enable the Active Directory System Discovery. In the following articles I’ll show you also the other discovery methods.

1.) Go to Site Settings and choose Discovery Methods
2.) Open the properties of Active Directory System Discovery
3.) Click on Enable Active Directory System Discovery
4.) Specify the location in your Active Directory you want to discover (root domain, OU level ect…)
5.) Specify the Polling schedule (when should the discovery proccess run)
6.) Enable Run discovery as soon as possible if the proccess must started directly!
7.) Specify the Active Directory attributes you want to discover
8.) After a copple of minutes go to you Computer Management, Collections, All Systems
9.) You’ll see your computer object from the Active Directory environment

SCCM_SD_01    SCCM_SD_02    SCCM_SD_03

SCCM_SD_04    SCCM_SD_05    SCCM_SD_06

SCCM_SD_07

How to: Prepare & Install SCCM 2007 on Windows 2003 Server

After preparing the Active Directory environment, we can start the installation of Microsoft System Center Cconfiguration Manager 2007. First of all, you’ve to enable some Windows Components:

1.) Internet Information Services (IIS)
2.) Enable network COM+ access
3.) Background Intelligent Transfer Services (BITS) Server Extensions
4.) Allow WebDAV Web Service Extensions

Now the environment is ready to start the installation. You can run the prerequisite checker to see if you’ve installed all the nessesary prequisites.

1.) The first site server is always the Primary SCCM server (Central Server)
2.) Choose the Custom settings, to specify your installation path, SQL server etc…
3.) The first server is always a Primary site
4.) Give the site a unique site code. This must be a unique 3 character code with a combination of letters, numbers or a combination of this two. For example S01, S02.
5.) Choose the mode for your SCCM environment. Note: for native mode requires a Public Key Infrastructure (PKI)
6.) Choose the agents you want to enable
7.) Specify the computername, instance and database name to store the SCCM database Note: Express Editions of SQL are not supported!!
8.) Enter the SMS Provider, used by the Configuration Manager Console to communicate with the site database
9.) Enter the FQDN of you Management Point. SCCM agents communite with the Management Point
10.) Specify the HTTP settings, default port 80 HTTP
11.) Download the latest updates to ensure the highest level of functionality and compatibility
12.) Check the settings summary
13.) Start the installation
14.) After the installation, check the following logfiles on your C:\ drive
     – ComponentSetup.log
     – ConfigMgrPrereq.log
     – ConfigMgrSetup.log

Install_SCCM_01    Install_SCCM_02    Install_SCCM_03

Install_SCCM_04    Install_SCCM_05    Install_SCCM_06

Install_SCCM_07    Install_SCCM_08    Install_SCCM_09

Install_SCCM_10    Install_SCCM_11    Install_SCCM_12

Install_SCCM_13    Install_SCCM_14    Install_SCCM_15

Install_SCCM_16    Install_SCCM_17    Install_SCCM_18

Install_SCCM_19    Install_SCCM_20    Install_SCCM_21

Install_SCCM_22    Install_SCCM_23    Install_SCCM_24

Install_SCCM_25    Install_SCCM_26    Install_SCCM_27

How to: Prepare Active Directory for installing Microsoft SCCM 2007

Before you can start the installation of Microsoft System Center Configuration Manager 2007 (SCCM 2007), you have the abbility to prepare the Active Directory environment. Note: If you’re not extend the Active Directory Schema, you’ve to use the Server Locator Point Role.

There are two ways to prepare your Active Directory environment.

1.) Running the EXTADSCH.exe from the installation media. This is a next, next, finish action.
2.) Import the schema extensions with LDIFDE. More actions, but a great logging option.

In my example I’ll use the LDIFDE tool, so the error reporting is much better.

1.) Copy the file CONFIGMGR_AD_SCHEMA.LDF to the local hard drive of your server. (you need to add the server name in this file!!)
2.) Open the file CONFIGMGR_AD_SCHEMA.LDF in Notepad
3.) Edit DC= in DC=DomainName. For example DC=SCCM,DC=LOCAL
4.) Open the command prompt
5.) Enter the following command ldifde -i -f .\CONFIGMGR_AD_SCHEMA.LDF -v -j .\log.txt
     * -i = Turn on Import Mode (The default is Export)
     * -f filename = Input or Output filename
     * -v = Turn on Verbose Mode
     * -j path = Log File Location
6.) Check the logfiles for any errors
7.) Give the SCCM Server full control permissions for performing the installation
8.) Open Active Directory Users & Computers
9.) Open the properties of the organizational unit System
10.) Go to the Security tab
11.) Add the new SCCM Server and give it Full Control to This object and all child objects
12.) Your Active Directory environment is now prepared for deploying SCCM 2007

SCCM_01    SCCM_02    SCCM_03

SCCM_04    SCCM_05    SCCM_06

SCCM_07    SCCM_08    SCCM_09

SCCM_10    SCCM_11    SCCM_12

SCCM_13    SCCM_14    SCCM_15

How to: Let domain users enable or disable the proxy server

In de most environments the users have a laptop for working in the office, but also for working out of the office. When there’s a proxy server enabled in your Internet Explorer settings, you’re able to internet on your office. But when you’re logging in out of the office, the proxy server is still enabled. So…..no internet for you!! In the most situations the Internet Explorer settings are hided through a GPO, so the users are not be able to edit the proxy settings manually. Whit the tool ProxyPal, you can give the users the oppertunity to enable or disable the proxy.

1.) Install ProxyPal on the laptop or computer (you can deploy it with a GPO)
2.) Edit your GPO’s to hide the Connection tab in your Internet Settings. (Optional!!)
3.) The users can enable or disable the proxy server now

ProxyPal_01    ProxyPal_02    ProxyPal_03

ProxyPal_04    ProxyPal_05    ProxyPal_06

ProxyPal_07    ProxyPal_08

How to: Recovering Deleted AD Objects in Windows Server 2008 R2

A new nice feature in Windows Server 2008 R2 is the Active Directory Recycle Bin. Deleted items can be restored without rebooting the Domain Controller(s), restarting the Active Directory Services and even without any backuptapes!! Let’s have a look on that.

The first step is to enable the Recycle Bin feature. Make sure your functional level is Windows Server 2008 R2 and keep in mind that when you enable this feature, you can’t disable this feature anymore!!

1.) Start the  Active Directory Module for Windows PowerShell
Import-Module ActiveDirectory

2.) View the actual settings of the Recycle Bin feature 
Get-ADOptionalFeature -Filter { name -like “Recycle*” }

3.) Enable the feature for your Active Directory environment 
Enable-ADOptionalFeature “Recycle Bin Feature” -Scope ForestOrConfigurationSet -Target E2K7SP2.LOCAL

4.) View all the deleted Active Directory objects 
Get-ADObject -SearchScope subtree -SearchBase “cn=Deleted Objects,dc=E2K7SP2,dc=LOCAL” -includeDeletedObjects -filter { name -notlike “Deleted*” }

5.) Restore the user objects you want 
Restore-ADObject -Identity “CN=User01\0ADEL:cc40dfd4-f671-4e90-90cc-3c8a33b18391,CN=Deleted Objects,DC=E2K7SP2,DC=LOCAL”
Restore-ADObject -Identity “CN=User02\0ADEL:394ec482-5bb2-4131-bdb4-7c92d7193987,CN=Deleted Objects,DC=E2K7SP2,DC=LOCAL”
Restore-ADObject -Identity “CN=User03\0ADEL:19f1bf8b-0227-486a-bc8d-ca72a342e116,CN=Deleted Objects,DC=E2K7SP2,DC=LOCAL”
Restore-ADObject -Identity “CN=User04\0ADEL:1b00b1c9-1f1f-4b74-b027-fa88feb4069d,CN=Deleted Objects,DC=E2K7SP2,DC=LOCAL”
Restore-ADObject -Identity “CN=User05\0ADEL:970b2597-4cf3-4971-87ea-9ada827e376d,CN=Deleted Objects,DC=E2K7SP2,DC=LOCAL”

6.) With this command you restore all the deleted items (Not Recommended!!)
Get-ADObject -SearchScope subtree -SearchBase “cn=Deleted Objects,dc=E2K7SP2,dc=LOCAL” -IncludeDeletedObjects -filter { name -notlike “Deleted*” } | Restore-ADObject

7.) All deleted Active Directory objects are restored now. Even the group membership of the users are restored!! Cool :D

AD_RCB_01

AD_RCB_02    AD_RCB_03    AD_RCB_04

AD_RCB_05    AD_RCB_06    AD_RCB_07

AD_RCB_08    AD_RCB_09    AD_RCB_10

AD_RCB_11    AD_RCB_12    AD_RCB_13

AD_RCB_14    AD_RCB_15

Exchange Server 2007 Supportability Matrix

With the release of Exchange 2007 SP2, the Microsoft Exchange Team has published a supportability matrix that identifies the various supported configurations of Exchange Server (operating system, Active Directory, Clients, .Net Framework, etc). You can find this document here.  Here are some notable guidelines from the article:

  • Exchange Server 2003 is not supported in Active Directory environments whose domain/forest functional levels have been raised beyond Windows Server 2003. However, Exchange Server 2003 SP2 can function against Windows Server 2008 Active Directory servers.
  • Exchange Server 2007 is not supported on Windows Server 2008 R2. However, Exchange 2007 SP1 RU9 and SP2 are supported against Windows Server 2008 R2 Active Directory servers. In addition, Exchange 2007 SP1 RU9 and SP2 are supported in Active Directory environments whose domain/forest functional levels have been raised to Windows Server 2008 R2.
  • Exchange 2007 SP2 is supported with PowerShell 2.0.

How to: Let domain users change there Power Scheme

In some environments users must have the ability to change the power scheme. By default, the normal Domain Users are not be able to do this, there’s an “Access Denied”. With the following Group Policy configuration, the Domain Users are albe to edit the Power Scheme on there laptop or PC.

1.) Make a new Group Policy and link it to the Organizational Unit where the computer objects are placed
2.) Go to Computer Configuration\Policies\Windows Settings\Security Settings\Registry
3.) Add the following registry hives
     HKEY_Localmachine\Software\Microsoft\Windows\CurrentVersion\Controls Folder\PowerCfg\GlobalPowerPolicy
     HKEY_Localmachine\Software\Microsoft\Windows\CurrentVersion\Controls Folder\PowerCfg\PowerPolicies
4.) Edit the permissions for the BUILTIN\Users from Read to Full Control
5.) Reboot your client
6.) Login with an user on that client
7.) The user has now the ability to change the Power Scheme

PW_01    PW_02    PW_03

PW_04    PW_05    PW_06

PW_07    PW_08    PW_09

PW_10    PW_11     PW_12

PW_13    PW_14    PW_15