Download details Update Rollup 2 for Exchange Server 2010 (KB979611)

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer]
“ShowDriveLettersFirst”=dword:00000004

Now you’re sure that the system drive will not be used by SCCM!

Download details Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB972076)

The last few mounths Exchange 2010 was my daily thing! Building…..building…..building and again building, this was the best preparing for me! A lot of things I’ve seen in Berlin at the TechEd, so I was ready to rock!

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\NonEnum\{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}]=dword:00000001

Core Configuration tasks include:

- Product Licensing
- Networking Features
- DCPromo Tool
- ISCSI Settings
- Server Roles and Features
- User and Group Permissions
- Share Creation and Deletion
- Dynamic Firewall settings
- Display | Screensaver Settings
- Add & Remove Drivers
- Proxy settings
- Windows Updates (Including WSUS)
- Multipath I/O
-Hyper-V including virtual machine thumbnails
- JoinDomain and Computer rename
- Add/remove programs
- Services
- WinRM
-Complete logging of all commands executed

You can download the tool here.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters and select the subkey Schema Version.

13 = Microsoft Windows 2000
30 = Original release version of Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 (SP1)
31 = Microsoft Windows Server 2003 R2
44 = Windows 2008

To fix this problem, you’ll need to do the following steps:

1.) On the SQL Server, right-click My Computer and select Manage to open the Computer Management console
2.) Expand the Local Users and Groups node and select Groups
3.) Double-click Administrators in the right-hand pane of the Computer Management console
4.) Click the Add… button to open the Select Users, Computers and Groups dialog box
5.) Click the Object Types… button and ensure Computers is selected in the Object Types dialog box. Click OK to return to the Select Users, Computers and Groups dialog box
6.) If the From this location field in the Select Users, Computers and Groups dialog box does not show the domain that the Configuration Manager site server is in, click the Locations… button and select the correct domain
7.) In the field labelled Enter the object names to select, type the computer name of the Configuration Manager site server. Click the Check Names to confirm that the name has been recognised
8.) Click OK

1.) Open the Exchange Management Console
2.) Navigate to Recipient Configuration, Distribution Group
3.) Click New Dynamic Distribution Group
4.) Give up  a Name and Alias
5.) Change the Filter settings. In this example I’m using the Active Directory attribute Department
6.) Give up the Filter Condition. To see a preview of all the effected users, click Preview
7.) Click New to finish the last step

This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052.

Download details Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534)

This version of Exchange is just really cool stuff!!

For more information, you can read this article on msexchangeteam.com

Robert Beauchemin
David Chappell
John Craddock
Tess Ferrandez
Rafal Lukawiecki
Andy Malone
Mark Minasi
Mark Russinovich
Ilse Van Criekinge
Maciej Pilecki

See you in Berlin…in the new efficiency!

——————————————-
We always talk about listening to customers and sometimes this is written off by many as ‘marketing speak’.  In fact, we do take feedback seriously and no input is more important to our engineering processes than your voice.

Earlier this year we made a decision in one direction, and due to the feedback we have received on this blog and elsewhere, we have reconsidered. In the coming calendar year we will issue an update for Exchange 2007 enabling full support of Windows Server 2008 R2. We heard from many customers that this was important for streamlining their operations and reducing administrative challenges, so we have changed course and will add R2 support.  We are still working through the specifics and will let you know once we have more to share on the timing of this update.

So, keep the feedback coming.  We are listening.

Kevin Allison
GM Exchange Customer Experience
——————————————-

So within a copple of months, there will be proberly full support for Exchange 2007 on Windows Server 2008 R2! This will be a great start of the new year 2010

Though this feature is good for security reasons it may be annoying for many users who use OWA regularly and they may not want to enter the password several times after the time out. This can settled down with a simple registry tweak on the CAS server that runs your Internet facing OWA site. This can be done by following registry modification:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeOWA
Name: PublicTimeout
Type: DWORD
Value: {value in minutes} (This value is 15 minutes by default)

The above suggestion applies only when the user selects the Public Computer option from the OWA logon screen. For the user who select the Private Computer from the logon screen you might want to modify:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeOWA
Name: PrivateTimeout
Type: DWORD
Value: {value in minutes} (This value is 8 hours by default)

If you don’t see the DWORD values named, PublicTimeout and PrivateTimeout then you have create then manually.

Server 1
Name: SRV-E2K10DC-01
OS: Microsoft Windows 2008 R2 x64
IP: 172.16.1.10
Roles: DC/DNS

Server 2
Name: SRV-E2K7-01
OS: Microsoft Windows 2008 SP2 x64
IP: 172.16.1.11
Roles: Exchange 2007 SP2 HT/CAS/MBX

Server 3
Name: SRV-E2K10-01
OS: Microsoft Windows 2008 R2 x64
IP: 172.16.1.12
Roles: Exchange 2010 HT/CAS/MBX

Domain FQDN: EXCHANGE.LOCAL
Forest Functional Level: Windows Server 2008 R2
Domain Functional Level: Windows Server 2008 R2

1.) First I’ve installed all the prerequisites for Exchange 2007 SP2 on server SRV-E2K7-01
Command: servermanagercmd -ip exchange-typical.xml
2.) Install all the prerequistes for Exchange 2010 on server SRV-E2K10-01
Command: servermanagercmd -ip exchange-typical.xml
3.) After rebooting server SRV-E2K7-01, you can install Exchange 2007 SP2
4.) After succesfully installing Exchange 2007 SP2, you can install Exchange 2010 on server SRV-E2K10-01
5.) Open the Exchange Management Console on server SRV-E2K7-01
6.) I’ve created some user account (100) and all mailbox enabled
7.) Open the Exchange Management Console on server SRV-E2K10-01
8.) As you can see, all the mailboxes are vissible!
9.) The next step is to move the mailboxes from Exchange 2007 to Exchange 2010
10.) Return to the Exchange 2010 server and open the Exchange Management Console
11.) Navigate to Recipient Configuration, Mailbox
12.) Select the mailboxes you want to migrate and right-click
13.) Choose “New Local Move Request”
14.) Select the new Mailbox Database
15.) Wait until the users are migrated to the new Mailbox Server
16.) Select all the completed move requests and select Clear Move Request

The users are now migrated to the new Exchange 2010 environment. In the next post we are going to de-install the Exchange 2007 environment.

FOR /L %i in (1,1,100) DO dsadd user “cn=User%i,ou=Gebruikers,dc=exchange,dc=local” -samid User%i -upn User%i@Exchange.local -fn User%i -display User%i -pwd P@sswOrd -disabled no

Chapter 1: Introduction to Exchange Server 2010
    1.1 Getting Started
    1.2 What’s been removed from Exchange Server 2010?
    1.3 What’s new in Exchange Server 2010?
    1.4 Exchange Server 2010 and Active Directory
    1.5 Exchange Server coexistence
    1.6 Exchange Server 2010 Server roles
    1.7 Summary
Chapter 2: Installing Exchange Server 2010
Chapter 3: Exchange Server 2010 Coexistence
    3.1 Coexistence with Exchange Server 2003
    3.2 Installing Exchange Server 2010 in an Exchange Server 2003 environment
    3.3 Coexistence with Exchange Server 2007
    3.4 Installing Exchange Server 2010 into an Existing Exchange Server 2007 Environment
    3.5 Summary
Chapter 4: Managing Exchange Server 2010
    4.1 The Exchange Management Shell
    4.2 The Exchange Management Console
    4.3 The Exchange Control Panel (ECP)
    4.4 Role Based Access Control (RBAC)
    4.5 Archiving and Compliancy
    4.6 Summary
Chapter 5: High Availability in Exchange Server 2010
    5.1 High Availability in Exchange Server 2010
    5.2 Exchange Server Database technologies
    5.3 High Availability in Exchange Server
    5.4 High Availability on other Server Roles
    5.5 Summary

This is my Exchange 2010 environment:

Server 1 – SRV-EXDC-01
OS: Microosft Windows 2008 R2 Enterprise x64
IP: 172.16.1.10
Roles: Active Directory, DNS

Server 2 – SRV-EX10HT-01
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 172.16.1.11
Roles: Exchange 2010 HT/CAS

Server 3 – SRV-EX10MB-01
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 172.16.1.12
Roles: Exchange 2010 MBX

Server 4 – SRV-EX10MB-02
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 172.16.1.13
Roles: Exchange 2010 MBX

1.) First I’ve created 2 new mailbox database on each mailbox server.
SRV-EX10MB-01 - MD01, MD02
SRV-EX10MB-02 - MD03, MD04
2.) The next step is to create a new Database Availability Group.
Groupname: DAG01
Witness Server: SRV-EX10HT-01 (Could also be a another server, but not a member of the DAG!!)
Witness Directory: C:\FSW_DAG01
3.) After succesfully creating the DAG, we can added some mailbox servers to it
SRV-EX10MB-01 and SRV-EX10MB-02
4.) The Windows Failover Clustering feature will automatically installed on each Mailbox server
5.) Give the Database Availability Group an IP address. This can be done with the following command:
Set-DatabaseAvailabilityGroup -Identity DAG01 -DatabaseAvailabilityGroupIpAddresses 172.16.1.50
6.) The next step is to add a Mailbox Database Copy
7.) The copy of the Mailbox Database will be copied to the other mailbox server. As you can see, Mailbox Server SRV-EX10MB-02 is now also containing Mailbox Database MD01 and MD02
8.) Login through the Outlook Web App with a user in Mailbox Database MD01
9.) Disable the LAN connection on Mailbox Server SRV-EX10MB-01 (fake a failover!)
10.) You’ll now receive an error in your Outlook Web App, this is normal, because the active mailbox is unavailable!! Wait a copple of seconds and click another e-mail message! As you can see, the passive Mailbox Database copy is now become active!! cool….
11.) After enabling the LAN connection on Mailbox Server SRV-EX10MB-01, the copy status become Healthy again!
12.) You can also test the “Fail Over” manually. Right click on your Mailbox Database, choose Move Active Mailbox Databse, and select the new active Mailbox Server.

So….after all, a copple of seconds downtime for the users!

Change the following rule:

Old Situation:
virtualHW.version = “6″

New Situation: 
virtualHW.version = “7″

After a reboot, everything works fine again!

As you increase the size of mailboxes, you don’t necessarily want all the data stored locally on user machines, because it can lead to very long initial download times when users get a new machine. The data users frequently access is stored in the primary mailbox, which is ideally less than 10GB and is cached locally. Everything else is stored in the archive mailbox and available online, so it can be much larger and contain historical data. Because the archive mailbox is part of the same mailbox database, its availability is the same as the primary mailbox (it will be replicated as part of a DAG, database availability group).

Users will see their mailbox and their archive mailbox. They can drag and drop a PST file into the archive and the PST will be imported into the archive automatically. The viewing and navigation of the primary and archive mailbox is the same. If a user searches all mail items, the archive content is included. Users or administrators can set retention policies so that mail is automatically moved to the archive after a number of days, and different policies can be set on different folders.

Here are some keynotes for the archiving feature in Exchange 2010:

- Archive mailbox gets rid of PST files by giving the user an additional mailbox
- PST files are local to the user’s machine, gets corrupted easily and is hard to include the files in backup.
- Archive mailbox sits in the same mailbox database as the user’s main mailbox and can be included in the backup easily
- Archive Mailbox is available in Outlook as well as Outlook Web App (OWA), which is a huge improvement.
- Users can access their email archive irrespective of where they are
- Archive Mailbox is included as part of the Exchange Enterprise CALs and hence no extra cost is required (for those who have ECALs)
- Retention policies can be set for emails/folders in the archive mailbox
- User has the option to search for emails in archive only or both primary & archive mailbox
- Archive Quota can be set separate to the primary mailbox
- Emails in existing PSTs can be dragged into the archive mailbox very easily
- The archive and primary mailbox share the same user account
- Only one archive mailbox can be configured for a user
- Archive mailbox gets created on the same mailbox database as the primary one, which is a drawback.
- Future service packs might bring the option to create the archive mailbox in a different database
- The default quota warning for the archive mailbox is 10GB, which can be changed

How to configure a archive mailbox for a specific user:

1.) Open the Exchange Management Console
2.) Navigate to Recipient Configuration and select the specific user
3.) On the action pane, select “Enable Archive”
Note: Online archiving requires an Exchange Enterprise Client Access License (CAL)!
4.) The icon of the specific user has changed to an archive  icon.
5.) Login to the Outlook Web App with the specific user and you’ll see the archive mailbox
6.) Drag and drop some e-mail into the online archive
7.) You can change the name of the online archive by navigating to the specific user, Properties, Mailbox Features, Archive
8.) Login again to the Outlook Web App and you’ll see the new name of the archive mailbox

You can fix this issueu to put some permissions on this Address Lists. Let’s have a look on that.

1.) Open the Exchange Management Console
2.) Create a new Address List
3.) Give up the filter settings (in this example it is based on the Active Directory field “Department“)
4.) Open ADSI Edit, adsiedit.msc
5.) Open Configuration,CN=Configuration,DC=E2K10.local,CN=Services,CN=E2K10,CN=Address Lists Container,CN=All Address Lists,<your Address Lists>
6.) Open the Properties, and click the Security tab, Advanced
7.) Disable “Include inheritable permissions from this object’s parent”
8.) Click Copy
9.) Remove the Authenticated Users
10.) Make a new Security Group in your Active Directory called for example “AL_ICT_Department”
11.) Place all the users of the ICT department in this Security Group
12.) Open the security settings again and at the group AL_ICT_Department
13.) Give this group the following permissions Read, Open Address List
14.) Login with a user that is member of the AL_ICT_Department. Make sure you see the Address List
15.) Login with a user that is not a member of the AL_ICT_Department. You didn’t see the Address List now.

When you pass Exam 70-662 TS: Microsoft Exchange Server 2010, Configuring, you complete the requirements for the following certification(s):

• Microsoft Certified Technology Specialist (MCTS): MIcrososft Exchange Server 2010, Configuration

Exam 70-662 TS: Microsoft Exchange Server 2010, Configuring: counts as credit toward the following certification(s):

• Microsoft Certified IT Professional (MCITP): Enterprise Messaging Administrator 2010

     – Exchange-all.xml
     – Exchange-base.xml
     – Exchange-cadb.xml
     – Exchange-cas.xml
     – Exchange-eca.xml
     – Exchange-edge.xml
     – Exchange-hub.xml
     – Exchange-mbx.xml
     – Exchange-typical.xml
     – Exchange-um.xml

In this example we are going to prepare a Microsoft Windows 2008 SP2 server for installing the Exchange 2010 Hub Transport Role, using the XML file Exchange-hub.xml.

1.) Open the command prompt (CMD)
2.) Browse to your installation source directory
3.) Type in ServerManagerCmd -ip Exchange-Hub.xml
4.) All prerequisites will be installed now
5.) After this is finished, you can start the installation of Exchange 2010

Some Enhancements:

• Microsoft Windows 7 and Windows Server 2008 R2 support.
• Building Blocks: import improvements
• Error Log: RES PowerFuse no longer depends on CAPICOM
• Home Directory Maintenance: provide a custom list of printers in PowerPrint
• Instant File Associations: automatic import of file types when adding applications
• Registry: disable removal of run keys
• Registry: fix Microsoft Windows Desktop Search
• Registry: force disconnect of RES PowerFuse session after a certain amount of time
• RES PowerFuse Agents: improved performance of Agent cache when processing changed objects
• Security Management: improved performance when checking logged security events
• Startup: improved performance when starting RES PowerFuse sessions using the Microsoft Windows shell

• Total Databases
• Total Database copies
• Total Exchange 2003 / 2007 / 2010 servers
• How many Exchange server with a specific role installed
• Total user mailboxes, distribution groups, contacts, legacy mailboxes

When you open the Exchange Management Consosle, go to Microsoft Exchange, Microsoft Exchange On-Premises. 

In Exchange 2010 Release Candidate (RC), there’s a new command available to move a mailbox to another mailbox database, New-Moverequest.

In this example I’m going to move all the mailboxes, including the default arbitration mailboxes to a new mailbox database, otherwise you can not delete the default mailbox database created by Exchange!

1.) With the following command you can get a list of all the Move Requests. Get-Moverequest | fl
2.) Run the command Get-Mailbox -Database “database name” -Arbitration | ft -wrap -auto for a list of all the hidden arbitration mailboxes in the default mailbox database
3.) To move the arbitration mailbox to the new mailbox database, run the following command New-MoveRequest -Identity “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” -TargetDatabase MD01
4.) After moving all the arbitraion mailboxes to the new mailbox database, run the following command Get-Moverequest | fl
5.) Before we can remove the default mailbox database, you’ve to remove all the move requests associated with the source mailbox database
6.) To get a list off all the associated move requests, run the following command Get-MoveRequest -SourceDatabase “Mailbox Database 1205181900″
7.) To remove the move requests, run the command Remove-Moverequest -<Recipient ID>
Note: For a list off all the Recipient ID’s you can run Get-Mailbox -Database “database name” -Arbitration | ft -wrap -auto
8.) After removing all the remove requests, you’re able to succesfully remove the default mailbox database

The fist step is to prepare the Schema.

1.) Open the root directory of the Exchange 2010 installation files
2.) Run the following command: .\Setup /PrepareSchema
Note: make sure you’ve SchemaAdmin rights

The next step is to prepare the Active Directory.

1.) Run the following command: .\Setup /PrepareAD /OrganizationName:<Your-Organization-Name>

The last step is to prepare the Domain.

1.) Run the following command: .\Setup /PrepareDomain
Note: make sure you’ve DomainAdmin rights

Your environment is now succesfully prepared to install Exchange 2010.

* Microsoft Windows 7
* Microsoft Exchange 2010
* Microsoft Windows Server 2008 R2

In this example i’ve added a new user with only permissions to read all the Packages.

1.) Open the System Center Management Console
2.) Navigate to the Site Database, Security Rights, Users, Manage ConfigMgr Users
3.) Add a new user, browse and select the new user
4.) Select “Add another right or modify an existing one”
5.) In this example the user has only the permission to read the packages
6.) Select in the Class box “Package”
7.) Select in the Instance box “(All Instances)”
8.) Finish the wizard

For remote connecting to the SCCM Site Server, you’ve to edit the DCOM security, otherwise you’ll receive an error when you try to open the System Center Management Console.

1.) Go to your SCCM Site Server
2.) From the Start menu, click Run and type Dcomcnfg.exe
3.) In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties
4.) In the My Computer Properties dialog box, on the COM Security tab, in the Launch and Activation Permissions section, click Edit Limits
5.) In the Launch Permissions dialog box, click Add
6.) In the Select User, Computers, or Groups dialog box, in the Enter the object names to select, in this example: markswinkels
7.) In the Permissions for markswinkels, select the check box to allow Remote Activation
8.) Click OK twice, and then close Computer Management

1.) Collection
2.) Package
3.) Program
4.) Distribution Point
5.) Advertisement

Before we are going to deploy Office 2007, we’ve to create a MSP file for customize the Office 2007 installation. You can start the Office Customization Tool using the following command: setup.exe /admin. Save the file in the updates folder on your Office 2007 source directory.

Step 1, creating a collection:
1.) Create a new collection, to specify the computers where Office must be installed.
2.) Navigate to System Center Configuration Manager, Site Database, Computer Management, New Collection
3.) Give your new collection a name, for example “Office 2007 Enterprise”
4.) On the Membership Rules dialog box, click the computer icon, which opens the Create Direct Membership Rule Wizard. Click Next
5.) On the Search for Resources dialog box, click the Resource class drop-down menu and select System Resource. Then, click the Attribute name drop-down menu and select Name. In the Value field enter %, and then click Next
6.) On the Collection Limiting dialog box, click the Browse button, select All Windows Workstation or Professional Systems, and then click Next
7.) Select the computer(s) you want to deploy Office 2007 and click Next

Step 2, creating a package:
1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Package, New Package
2.) On the General dialog box of the New Package Wizard, enter the Name, Version, Manufacturer, and Language. For example, Office, 2007, Microsoft, English (US)
3.) On the Data Source dialog box, select This package contains source files. Click the Set button, and then enter the path for the location of the source files in the Source directory field. For example E:\Software\Office 2007\, which contains a copy of the 2007 Office Enterprise installation CD.
4.) Click OK, and then continue to click Next and accept the default settings on all of the following dialog boxes: Data Access, Distribution Settings, Reporting, and Security. On the Wizard Completed dialog box

Step 3, creating a Program:
1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Packages, Office 2007, Programs, New, Program
2.) Give the new program a Name
3.) On the Command-line box, type in setup.exe (Because the customization file, CustomOffice.MSP, was placed in the \Updates folder, a command line option is not needed to reference its location)
4.) On the Environment dialog box, click the Program can run drop-down box and select Whether or not a user is logged on. This will enable Run with administrative rights for the Run mode. Leave the default for Drive mode to Runs with UNC name, and then click Next
5.) On the Advanced dialog box, select the check box for Suppress program notifications, and then click Next

Step 4, Copy to Distibution points:
1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Packages, Office 2007, Distribution points
2.) Manage Distribution Points
3.) Select “Copy the package to new distribution points”
4.) Select the distribution points
5.) Click finish and wait a copple of minutes
6.) Check the status changing from Install Pending to Installed

Step 5, creating the advertisement
1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Advertisements
2.) New Advertisement
3.) Give the advertisement a Name
4.) Select the package, Program and Collection
5.) Click finish and wait a copple of minutes
6.) On the client wait for the next Machine Policy Retrievel & Evaluation Cycle

After the setup is finished, Office 2007 is deployed to your client(s) and is ready to use!

1.) Open your control panel
2.) Configuration Manager
3.) Action tab
4.) Machine Policy Retrieval & Evaluation Cycle
5.) Initiate Action

The next option is to use the following script.
———————————————————————————————
on error resume next

dim oCPAppletMgr ‘Control Applet manager object.
dim oClientAction ‘Individual client action.
dim oClientActions ‘A collection of client actions.

‘Get the Control Panel manager object.
set  oCPAppletMgr=CreateObject("CPApplet.CPAppletMgr")
if err.number <> 0 then
    Wscript.echo "Couldn’t create control panel application manager"
    WScript.Quit
end if

‘Get a collection of actions.
set oClientActions=oCPAppletMgr.GetClientActions
if err.number<>0 then
    wscript.echo "Couldn’t get the client actions"
    set oCPAppletMgr=nothing
    WScript.Quit
end if

‘Display each client action name and perform it.
For Each oClientAction In oClientActions

    if oClientAction.Name = "Request & Evaluate Machine Policy" then
        wscript.echo "Performing action " + oClientAction.Name
        oClientAction.PerformAction
    end if
next

set oClientActions=nothing
set oCPAppletMgr=nothing
———————————————————————————————

————————————————————————————–
Dim ClientResource
Set ClientResource = CreateObject(“UIResource.UIResourceMgr”)
Set CacheInfo = ClientResource.GetCacheInfo
CacheInfo.TotalSize = 10000
————————————————————————————–

- Microsoft Application Virtualization Sequencer:
The Application Virtualization Sequencer ‘program’ is used to package virtual applications for deployment with Configuration Manager.

- Configuration Manager Site Server:
A part of the Configuration Manager Site hierarchy, the Configuration Manager Site Server manages virtual application distribution through
Configuration Manager Distribution Points to target systems, either as a streaming service, or as a locally delivered package.

- Configuration Manager Distribution Point (Distribution Point):
Configuration Manager Distribution Point site roles provide management services such as hardware and software inventory, operating system deployment, and software updates, as well as software distribution of both physical and virtual applications, to Configuration Manager target systems (often referred to as ‘clients’).

- Configuration Manager / Application Virtualization Clients:
Client devices include desktop/laptop PCs, terminal servers and Windows Vista Enterprise Centralized Desktop (VECD) clients.  Configuration Manager Clients that receive delivery of virtual applications from a Configuration Manager infrastructure require both the Configuration Manager Advanced Client and Application Virtualization Client software to be installed and configured.  The Configuration Manager and Application Virtualization Client software work together to deliver, interpret and launch virtual application packages.  The Configuration Manager Client manages the delivery of virtual application packages to the Application Virtualization Client. The Application Virtualization Client executes the virtual application on the client PC.

Configuration Manager and Application Virtualization Software Requirements:

- A healthy Configuration Manager infrastructure:
It is critical to ensure that the customer’s Configuration Manager infrastructure is healthy before enabling Configuration Manager’s virtual application management features.

Below you’ll find a list of the minimum Configuration Manager infrastructure components required for virtual application management with System Center Configuration Manager R2.

- Primary Site:
A Configuration Manager Primary Site with Configuration Manager 2007 SP1 + Configuration Manager 2007 R2 installed

- Site Server:
A Configuration Manager Site Server configured with the following site server roles:
     – Site System
     - Site Server
     – Component Server
     – Distribution Point
     – Fallback Status Point
     – Management Point
     – Reporting Point

- Distribution Point Servers:
One or more standard Distribution Point servers or Branch Distribution Point servers.  The use of a Branch Distribution Point requires at least one standard Distribution Point

- Clients:
One or more Configuration Manager Client PCs

Below you’ll find a list of the minimum Application Virtualization 4.5 infrastructure components required for virtual application management with System Center Configuration Manager R2.

- Application Virtualization Sequencer
     – Required to sequence applications
     – 4.5.0.1485 or later

- Application Virtualization Client for Windows Desktops
     – Required to run virtual applications on desktop and laptop PCs
     – 4.5.0.1485 or later

- Application Virtualization Client for Terminal Services
     – Required to run virtual applications on Windows Terminal Servers
     – 4.5.0.1485 or later

Book content:

1.) Microsoft’s Virtualization Solution
2.) Server Virtualization – Hyper-V
3.) Managing Virtualization – VMM 2008
4.) Application Virtualization – App-V
5.) Presentation Virtualization – Terminal Services
6.) Desktop Virtualization – MED-V and VDI
7.) User State Virtualization
8.) Building a Virtualization Infrastructure

Click the image below to optain a copy! 

In this example we are going to enable the Hardware Inventory Client Agent, so we know what hardware is available in our environment.

1.) Go to the Site Management, Your site name, Site Settings, Client Agents, Hardware Inventory Client Agent
2.) Open the properties
3.) Enable the “Enable hardware inventory on clients”
4.) Select a schedule interval
5.) On the client wait for the next “Machine Policy Retrieval & Evaluation Cycle” (to run this action directly, select “Initiate Action”)
6.) You’ll now see an extra action on your client “Hardware Inventory Cycle”
7.) On the client wait for the next “Hardware Inventory Cycle” (to run this action directly, select “Initiate Action”)
8.) Wait a few minutes so that all the collected items are commited into the Site Database
9.) Go to the Computer Management, Collections, All Systems
10.) Select the computer you want to view, right click, Start, Resource Explorer
11.) Now you see all the hardware of this computer

1.) Open your SCCM Management Console
2.) Go to Site Management, your site name, Site Settings, Site Maintenance, Tasks
3.) Here you see “Backup ConfigMgr Site Server”
4.) Open the properties of “Backup ConfigMgr Site Server”
5.) Enable this task, set the backup paths and select the schedule interval
     – Note: when your SCCM Database is on a different server, there’s a folder created on the E:\ drive of that server!
     – For exameple: one folder on server SRV-SCCM01 and one folder on server SRV-SCCM02.
6.) When you want to start the backup manual, you can start the following service on your SCCM Site Server
     – SMS_SITE_BACKUP
7.) Your SCCM environment is now succesfully backuped with exactly the same time stamps.

- Client push
- Software Update point
- Group Policy
- Manual
- Loginscript
- Software Distribution
- Imaging

In this example we are going to push the client to our servers and workstations.

1.) First you need to configure your boundaries. I’ve added a IP range of my workstation DHCP scope. This can also be:
     – IP subnet
     – Active Directory site
     – IPv6 prefix
     – IP address range
2.) Now we can enable the client push installation. Go to Site Management, your site name, Site Settings, Client Installation Methods, Client Push Installation.
     – Enable: “Enable Client Push Installation to assigned resources”
     – System types: Choose the system types where you want to install the SCCM clients
     – Accounts: Type in a account with administrator rights
     – Client: Type in the installation properties. In this example I’m using only the option SMSSITECODE=S01. For an overview of all the options, check the following link: http://technet.microsoft.com/en-us/library/bb680980.aspx
3.) Make sure you’ve run an discovery, so the system where you want to install the client is succesfully discovered
4.) In order to successfully use client push to install the Configuration Manager 2007 client, you must add the following as exceptions to the Windows Firewall:
     – File and Printer Sharing
     – Windows Management Instrumentation (WMI)
5.) Right click on the system where you want to install the SCCM client and select Install Client
6.) After starting the installation, you’ll see the following proccess on your client
     – CCMSETUP.EXE, this is a sign that the installation is running
7.) When the installation is finished, there’s a new proccess CCMEXEC.EXE
8.) Verify that the agent is succesfully installed. Go to your control panel on your client and check the following new icons:
     – Configuration Manager
     – Remote Control
     – Run Advertised Programs

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

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

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

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

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

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

• 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.

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

You can download Exchange 2007 Serivce Pack 2 here.

Once you install the update, you can enable one or more of the following tools from the Control Panel under Programs, Turn Windows features on or off.

You can download RSAT here.

“Stand alone DC/GC can be Windows Server 2008 R2 and it is supported to have Exchange Server 2007 SP2 work against these DC/GCs.
There is NO support for any Exchange Server 2007 SP2 components (any roles, including admin tools) installed on Windows Server 2008 R2. Exchange Server 2007 SP2 will not even install on it – the pre-req check will fail during installation.”

So when you’re planning to upgrade to Microsoft Windows 2008 R2, keep in mind that you not upgrade your Exchange 2007 environment!

1.) First make some new INI file in your Flex_Config\ProfileSettings directory
2.) Edit the INI file and type in the RegisterTree or IndividualRegistryValues
3.) Login to your Terminal Server environment, start Adobe Reader and make some changes
4.) Logoff and check the users home directory if there’s a file called <INIfilename.ZIP> in my example AdobeReader9.ZIP. In this file you see all the registry settings!
5.) Login again and see that the settings are saved
6.) Delete the <INIfilename.ZIP> from the users home directory
7.) Login again to your Terminal Server environment
8.) As you can see, all the settings are gone!
9.) If you want to replace a backup, in the users home directory folder _Settings\Settings_Backup is a backup available automatically

I’m going to install this tool in my Windows 2003 Terminal Server environment.

– First install the Immidio Flex Profile application on your Terminal Server(s). When executing the Immidio Flex Profiles.msi file, no services are installed and no reboots are required. The Flex Profiles MSI file must be executed under an account with administrative privileges, since a small number of registry keys are added to the HKEY_LOCAL_MACHINE hive.
Note! To install the Framework unattended, just run the following command. msiexec /i “\\Server\Share\Immidio Flex Profiles.msi” /qn

– The Flex Profiles framework includes a compressed file that is used for central configuration purposes: Flex_Config.zip. Extract this file in a central and fault tolerant network share using a Zip program, such as WinZip. The target folder can be a share on a file cluster or the NETLOGON share or SYSVOL folder on a domain controller. The scripts included in Flex_Config.zip help you to centrally configure Flex Profiles.

– Configuring the Flex Profiles in the logon and logoff script is rather simple. The syntax to activate Flex Profiles is as follows.

An example for a logon script may look as follows.
CSCRIPT /NOLOGO “%PROGRAMFILES%\Immidio\Flex Profiles\Flex_Framework.vbs” LOGON \\FLEX.local\NETLOGON\Flex_Config

In the logoff script, specify the LOGOFF option instead:
CSCRIPT /NOLOGO “%PROGRAMFILES%\Immidio\Flex Profiles\Flex_Framework.vbs” LOGOFF \\FLEX.local\NETLOGON\Flex_Config

IMPORTANT: Proper timing is essential when setting up Flex Profiles in a user logon script. It is recommended to run the Flex Framework script in the logon script after the home directories are mapped and before other application settings are configured. Additionally it is recommended to enable the policy Run logon scripts synchronously in order to prevent applications or the desktop from starting while the logon script is still running.

– In order to configure the Flex Profiles Framework the file Framework.ini in the Flex configuration folder needs to be opened and modified with an adequate ANSI editor, such as Notepad.

I’ve edit this setting to [LOCATIONS] STOREROOT, this setting configures the root of the path where the profile archives are stored.
STOREROOT=3 uses the user’s Terminal Server home directory directly from AD (Only supported with Windows Server 2003 and Windows Server 2008 in an AD environment). By default the vallue is 1.

– After you login on your Teminal Server environment, and you logoff, you’ll see the following folder in your users home directory _Settings. Here are the user specific settings that will be saved when the users are logoff. As you can see, all the .ZIP file are exactly the same as in your NETLOGON directory, were you can make you settings per application! You  can add new INI files if you want to add some application settings, or even delete some INI files from appliations that are not used in your environment.

SCC (Single copy cluster)
was what I would call a traditional Exchange cluster which used shared storage to host the Exchange database.

CCR (cluster continuous replication)
was used to replicate Exchange database information between 2 Exchange server allowing for hardware and storage redundancy but was limited to 1 Active node and 1 Passive node.

SCR (standby continuous replication)
was introduced in Exchange 2007 SP1 to provide the ability to replicate Exchange databases to an disaster recovery location.

– Enter the productkey:
slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

– Activate Windows:
slmgr.vbs -ato

– Rename the computer:
Netdom renamecomputer “%computername%” /newname:SRV-RODC01 /reboot:15

– Show all network interfaces:
Netsh interface ipv4 show interface

– Set a static IP address:
Netsh interface ipv4 set address name=2 source=static address=172.16.1.11 mask=255.255.0.0 gateway=172.16.1.1
(make sure that you’re choosing the right network interface. In this example it’s 2, so name=2 it means interface 2)

– Set a static DNS server:
Netsh interface ipv4 add dnsserver name=2 address=172.16.1.10 index=1

– Turn Remote Desktop (RDP) on:
Cscript %windir%\system32\SCRegEdit.wsf /ar 0

– Enable Remote Desktop (RDP) in the Windows Firewall:
netsh advfirewall firewall set rule group=”remote desktop” new enable=yes
(Note: type this rule in by your self, copy past will give an error!)

– Enable Remote Management (RemoteCMD) in the Windows Firewall:
netsh advfirewall firewall set rule group=”Remote Administration” new enable=yes
(Note: type this rule in by your self, copy past will give an error!)Making the unattended.txt:
Copy and past the following test into the new textfile and save this file on the C: drive of the Core Server.
==================================================
[DCInstall]
InstallDNS=Yes
ConfirmGc=Yes
CriticalReplicationOnly=No
DisableCancelForDnsInstall=No
Password=********
RebootOnCompletion=No
ReplicaDomainDNSName=GPO.local
ReplicaOrNewDomain=ReadOnlyReplica
ReplicationSourceDC=srv-w2k8dc01.gpo.local
SafeModeAdminPassword=********
SiteName=Default-First-Site-Name
UserDomain=GPO.local
UserName=Administrator
==================================================

 – Run the DCPROMO
dcpromo /unattend:c:\unattend.txt15)

– Reboot the Domain Controller
shutdown -r -t 0

As you can see, when you make a connection to the RODC, you’re not be able to make any changes to existing users or groups and the option “New” is hidden when you right-click in your environment.

In the next post i’m going to delete a RODC from the environment. (for example if your server is stolen or something like that).

The first step is to create a fresh Mandatory Profile.

1.) Create a new local user on a Windows 2003 Server machine and make that user member of the Local Administrators Group.
2.) Login with that that user.
3.) Make your changes.
4.) Right-click on your computer, Properties, Advanced, Settings (unther User Profiles).
5.) Select your template user and click Copy To
6.) Browse to your share on your server.
7.) Change Permitted to use to Everyone Full Controll.
8.) The last step is to rename your NTUSER.dat to NTUSER.man, this makes your profile Mandatory (Read-Only).

Now we’re going to publish this mandatory profile to all the RES PowerFuse Agents, so the Mandatory profile is present on each PC with the RES PowerFuse Agent.

1.) Open your RES PowerFuse Management Console.
2.) Click on RES PowerFuse Setup, Datastore, Custom Resources
3.) Click on Add, browse to your Mandatory Profile share

As you can see, there’s now your Mandatory Profile. It will be published to all the RES PowerFuse Agents. The default location is: C:\Program Files\RES PowerFuse\Data\DBCache\Resources\custom-resources

The last step is to edit the profile path from your Active Directory Users.

1.) Open Active Directory Users and Computers on your Domain Controller.
2.) Locate your users
3.) Select one or more users and click Properties
4.) Go to the Terminal Services Profile tab
5.) Type in the path to the local Mandatory Profile
C:\Program Files\RES PowerFuse\Data\DBCache\Resources\custom_resources\Mandatory-2003

Now the users are ready to login on your Terminal Server environment with RES PowerFuse.

For this example I’ve deleted the OU (Organizational Unit) where my computer objects are placed. The consequenses….Yes, the computers are not longer trusted to this domain, OOPS!!

By default the Active Directory markes all the deleted objects as IsDeleted True. The objects are not vissible any more in your Active Directory, but they still there. This calls tombstoned objects. By default tombstoned objects will be available for 60 days in a Windows 2000/2003 Active Directory and 180 days in a Windows 2003 SP1 of 2008 Active Directory.

As you can see, I’ve deleted the OU Omgeving with the sub OU’s Laptop and PC and all the computers objects in this OU’s. Now we’re going to restore everything back! Note: make sure you first restore the highest OU, than the sub OU’s and finally the computer objects.

1.) Start the command prompt (Start, Run, CMD)
2.) Locate ADRESTORE.EXE
3.) Type in ADRESTORE -R Omge* (this will find all deleted object starting with Omge)
4.) Restore the OU Omgeving by pressing Y
5.) Type in ADRESTORE -R Lap* (this will find all deleted object starting with Lap)
6.) Restore the OU Laptop by pressing Y
7.) Type in ADRESTORE -R PC
8.) Restore the OU PC by pressing Y
9.) Type in ADRESTORE -R PC* (this will find all deleted objects starting with PC)
10.) Restore the computer objects PC01 till PC10 by pressing Y
11.) 9.) Type in ADRESTORE -R LT* (this will find all deleted objects starting with LT)
10.) Restore the computer objects LT01 till LT10 by pressing Y

When you’ve restored all the objects, these are disabled by default, so you’ve to enabled them manually!

Well, I’ve done the scouring for you and the default password is wSS2008!

Hopefully that helps someone out!

- Drive Maps
- Environment variables
- Files
- Folders
- Ini files
- Registry keys
- Shortcuts

In my testenvironment I’ve build a custom start menu for the user in my environment. You can do this by using the User Preferences. When you’re using Item-Level targeting, you can manage what users are getting some shortcuts. In this example I’m using Item-Level targeting with Security Groups, so when a user is member of a specific security group, he’ll receive the shortcut in his start menu.

1.) First make a new Group Polciy
2.) Go to User Configuration, Preferences, Windows Settings, Shortcuts
3.) Create a new shortcut
4.) Fill in the right path’s **picture 3**
5.) Go to the Common tab
6.) Enable “Remove this item when it is no longer applied” (note: this will change the “Action” to Replace)
7.) Enable “Item-level targeting” and click “Targeting”
8.) Select the way off targeting (note: in this example I’m using Security Group)
9.) Make the right users members of the security group
10.) Logon to your workstation and check your start menu

As you can see, based on the group membership, User01 get’s his shorcuts to the different applications. This can also be configured on the other User Preferences.

Update Rollup 9 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

Get-EventLog *
(gives an overview of all the available event sources)

When you put the following commands into a PS1 file and schedule it on a specific server, you’ll receive the event logs in an e-mail!
(in this example you’ll receive an e-mail from eventviewer@e2k10.local with the 10 newest event logs)

—————————————————————————
$body = Get-EventLog -LogName “dns server” -Newest 10 | out-string
$From = “eventviewer@e2k10.local”
$to = “administrator@e2k10.local”
$server = “srv-exc2010.e2k10.local”
$subject = “Event Viewer – srv-exc2010.e2k10.local”
$msg = new-object System.Net.Mail.MailMessage $From, $to, $subject, $body
$client = new-object System.Net.Mail.SmtpClient $Server
$Client.Send($msg)
—————————————————————————

All the userprofiles are still there when the user logoff, included only one directory and one file…hgfs.dat. The file hgfs.dat comes from VMware shared folder feature. The files is created in the profile of the first user that logs on. The file handle is kept open and therefore you might get more profile folders for the same user.

I’ve fixed it with the following VMware (VMware FAQ1317) article.

1.) Open regedit on your Terminal Server
2.) Locate the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
3.) Edit the key ProviderOrder
4.) Remove vmhgfs
5.) Close regedit
6.) Reboot your Terminal Server

As Edwin says on his blog, “So to the Dutch community I want to say lets go and let us build a real cool CUG together”. Guys, congratulations with this new CUG and let’s hope it will be very succesfull! See you on the forums

1.) Open the RES Wisdom Management Console
2.) Open RES Wisdom, Infrastructure, Agents
3.) Right-click and select Add
4.) Select the target computer
5.) Select agent and click Deploy now…
6.) Enter some admin credentials to perform the installation
7.) On the target computer you’ll see the process WISDeploy.exe
8.) After the installation fished succesfully, there’s a new service running on the target computer. RES Wisdom Agent Service.
9.) Now you see there’s one agents available in your RES Wisdom Management Console.

let’s update the Address Lists!

Set-AddressList “All Users” -IncludedRecipients MailboxUsers

Set-AddressList “All Groups” -IncludedRecipients MailGroups

Set-AddressList “All Contacts” -IncludedRecipients MailContacts

Set-AddressList “Public Folders” -RecipientFilter { RecipientType -eq ‘PublicFolder’ }

“Unable to edit the specified E-mail address policy. E-mail address policies created with legacy versions of Exchange must be upgraded using the ‘Set-EmailAddressPolicy’ task, with the Exchange 2007 Recipient Filter specified.”

Oké, let’s update the recipient policy! With the following command you can see the properties of this recipient policy.

Get-EmailAddressPolicy | fl Name,*RecipientFilter*,ExchangeVersion

Set-EmailAddressPolicy “Default Policy” -IncludedRecipients AllRecipients

After running this commands, you’re able to edit the “Default Policy” again.

For a overview off all the options after the pipe command, you can the following command.

Get-Mailbox -Identity <useralias> | fl

Get-Mailbox | fl UserPrincipalName, ServerName, PrimarySMTPaddress, Emailaddresses

1.) Open the Internet Information Services (IIS) Manager
2.) Navigate to the Web Sites, Default Web Sites
3.) Creat a new Virtual Directory with the alias Iisadmpwd
4.) Browse to the following path: C:\Windows\System32\Inetsrv\Iisadmpwd
5.) Allow the following permissions: Read, Run scripts, Execute
6.) Enable the change password button in OWA by opening regedit and create the following REG_DWORD – DisablePassword with the value 0 (zero)
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\OWA
7.) Register the following DLL from the command prompt.
regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll
8.) Restart your IIS Server with the command iisreset /noforce

       

get-mailboxserver Servername | add-adpermission -user svc-backup -accessrights GenericRead, GenericWrite -extendedrights  Send-As, Receive-As, ms-Exch-Store-Admin

1) Backup your SQL 2005 databases
2) Backup your RMS encryption key
3) Backup your IIS metabase
4) Backup your management packs (unsealed)
5) Backup your files
6) Backup your registry

Step 1) Backup your SQL 2005 databases
First off al we are going to backup the SQL 2005 databases.
- OperationsManager
- ReportServer
- ReportServerTempDB
       

Step 2) Backup your RMS encryption key
The next step is to backup the RMS (Root Management Server) encryption key.
We are going to use the tool SecureStorageBackup.exe, located in the installation directory of SCOM 2007.
       

Step 3) Backup your IIS metabase
The next step is to backup the IIS metabase.
       

Step 4) Backup your management packs (unsealed)
Now we are going to backup the unsealed management packs. The sealed management packs can be downloaded from the vendor’s website again.
       

Step 5) Backup your files
The next step is to backup the SCOM 2007 configuration files. Make sure you backup the following directory.(in my example!!)
- C:\Program Files\System Center Operations Manager
This can also be different, but this is the installation directory of your SCOM 2007 environment.
- C:\Program Files\System Center Management Packs
This is the defualt location of your sealed management packs.

Step 6) Backup your registry
The last step is to backup some registry keys. Make sure you backup the following registry keys.
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager
HKEY_CURRENT_USER\Software\Microsoft\Microsoft Operations Manager
   

Update Rollup 8 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

• 948856  Event ID 9667 occurs when you create a new named property on an Exchange Server 2007 server
• 952935  A software update is available that provides the log tracing feature for the LogTruncator tag in Exchange Server 2007
• 954639  Exchange Information Store service stops responding intermittently on an Exchange 2007 server
• 955480  Meeting requests from external senders are displayed as Busy instead of Tentative in an Exchange 2007 environment
• 956633  User calendar permissions are removed after you run the Set-MailboxCalendarSettings cmdlet in an Exchange Server 2007 environment
• 957640  The “test-*” command fails when you run it on a site that contains only CAS roles in an Exchange 2007 environment
• 958239  Exchange Server 2007 does not generate an event log message for public folder replication messages even though a property validation exception is thrown and the replications do not occur
• 958881  All HTML content in attachment files of messages is run through an HTML filter when you open or save the attachment by using Outlook Web Access (OWA)
• 958938  The importance attribute of a message is lost when an Exchange 2007 user accesses a high-importance message or a low-importance message from Exchange Server 2007 by using a non-Outlook POP3 client or IMAP4 client
• 959510  A meeting request that is sent from OWA causes a “553 5.0.0 Message-Id header line format error” NDR message in an Exchange Server 2007 environment
• 959748  An account with the “Exchange View-Only Administrator” permission can review user mailbox contents by using an administrative application in Exchange Server 2007
• 959861  Some clients cannot connect to back-end Exchange Server 2003 IMAP servers after Exchange 2007 Service Pack 1 RU2 is applied
• 959990  An error occurs when you try to update a recurring appointment by using an Outlook client that is connected to an Exchange 2007 server
• 960178  You receive an NDR when you send an e-mail using OWA Premium and the ANR cache if the Exchange organization name has more than one space
• 960354  Edge Attachment Filtering does not honor the ExceptionConnectors value in Exchange Server 2007
• 960367  Error message when you run the Export-Mailbox command on a folder that has more than 5000 items in Exchange 2007: “-1056749164″
• 960495  The Information Store service crashes continuously on an Exchange Server 2007 server
• 960633  The Microsoft Exchange Information Store service crashes on an Exchange Server 2007 that has the mailbox server role installed
• 960703  Extended characters are replaced by question marks when you send an e-mail message that contains extended ASCII characters by using an IMAP4 client in Exchange 2007
• 960775  You receive a “Message too large for this recipient” NDR that has the original message attached after you restrict the Maximum Message Send Size value in Exchange Server 2007
• 960869  A queue that has multiple connections cannot enter a Retry state in Exchange Server 2007
• 961152  The Exchange information store service (Store.exe process) crashes intermittently when you migrate user data from Lotus Notes to Exchange Server 2007
• 961347  Error message when you export an Exchange 2007 mailbox to a .pst file and a filter is defined: “Export-Mailbox : Error was found for &lt;username&gt; (&lt;SMTP address&gt;)”
• 961443  Users cannot use Outlook Web Access for Exchange Server 2007 to open an address book
• 961524  Some journal messages are stuck in the Submission queue in Exchange Server 2007
• 961606  After you apply Rollup Update 5 for Exchange Server 2007 S961606, Outlook Web Access users find the font size of plain text messages is extremely small when they use some third-party Web browsers
• 961693  Japanese (1 byte Kana) characters in the subject and display name are corrupted when you try to reply or forward task requests or calendar items in Outlook client
• 962235  The date and time information for a “Follow Up” flag is missing if an Exchange 2007 user sends a message to an external recipient
• 966535  Duplicate messages are sent to an external recipient if the recipient is included in multiple distribution lists in an Exchange Server 2007 environment
• 967038  Many log entries are generated in Exchange Server 2007 if you turn on the Exchange log to audit the logons that do not use the primary account for shared resource mailboxes
• 967097  Users may receive duplicate calendar items for the updated instance on mobile devices
• 967109  A delegate cannot accept a meeting request for an online meeting in an Exchange Server 2007 environment
• 967255  Only the tracing information of the last user is logged when you configure Exchange Server 2007 to trace multiple users at the same time
• 968310  Many log entries are generated on an Exchange Server 2007 computer when you enable the Exchange log to audit user logons that do not use the primary account for their mailbox
• 968352  The W3wp.exe process crashes when you use the Italian version of the spelling checker on a message in Outlook Web Access in Exchange 2007
• 968589  The managed policy does not work if the ptagProvisionedFid attribute is missing in Exchange Server 2007
• 968673  The EdgeTransport.exe file of Exchange 2007 servers crashes continuously and Event ID 10003 and Event ID 5000 occur
• 968745  Incomplete tasks show in the Complete tasks view in OWA 2007 in an Exchange 2007 environment
• 968966  Many log entries are generated in Exchange Server 2007 if you turn on the Exchange log to audit administrator logons that do not use the primary account for mailboxes
• 969690  Unresolved sender for delivery status notifications after applying update rollup 7 for Exchange Server 2007 Service Pack 1
• 970687  A search operation in Outlook does not return a correct result if there is a corrupted HTML message in the target folder in an Exchange Server 2007 environment

————————————————————————————
The mailbox database ‘DB01′ cannot be deleted.

DB01
Failed
Error:
This mailbox database contains one or more mailboxes or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. Arbitration mailboxes should be moved to another server; run the command Move-Mailbox <Mailbox ID> -Arbitration -TargetDatabase <Database ID>.  To remove the arbitration mailbox if this is the last server in the organization, run the command Remove-Mailbox <Mailbox ID> -Arbitration -RemoveLastArbitrationMailboxAllowed.
————————————————————————————

You cannot remove the database, because there are some mailboxes in it. Oké….let’s have look what mailboxes are left in this mailbox database.

Get-Mailbox -Database DB01

As you can see, there are no mailboxes left in de mailbox database, but why we are still receiving this error!! This is the answer…….there are two hidden mailboxes left in de mailbox database, called arbitration mailboxes. With the following command you’re able to see this mailboxes

Get-Mailbox -Database DB01 -Arbitration | ft -wrap -auto

When you move these two mailboxes to another mailbox database, all the error messages are gone! So let’s do that!

Move-Mailbox “SystemMailbox{1f05a927-3be2-4fb9-aa03-b59fe3b56f4c}”  -Arbitration -TargetDatabase DB02
Move-Mailbox “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}”  -Arbitration -TargetDatabase DB02

—————————————————————————————————
Get-DistributionGroup | select name , alias ,EmailAddresses | foreach {
  “Name: “+$_.name
  “Alias: “+$_.alias
   $_.EmailAddresses | foreach {
     if($_.SmtpAddress){
     “SmtpAddress: “+$_.SmtpAddress
   }
}
write-host
}
—————————————————————————————————

When you copy and past this code in notepad and save it as Get_Dis.ps1 , you get the following export for example:

Name: Exchange Team
Alias: ExchangeTeam
SmtpAddress: Exchange2003Team@e2k7.local
SmtpAddress: Exchange2007Team@e2k7.local
SmtpAddress: ExchangeTeam@e2k7.local

Name: ICT Helpdesk
Alias: ICTHelpdesk
SmtpAddress: Helpdesk@e2k7.local
SmtpAddress: ICTHelpdesk@e2k7.local

Name: ICT Management
Alias: ICTManagement
SmtpAddress: ICTManagement@e2k7.local

In this example i’ve choosen for the “Automaic Computer Discovery”. With the “Advanced Discovery” you’ve some more options to discover you’re clients and servers, for example with a custom LDAP query on your Active Directory to find a specific client or server in your environment.

First off all install the following prerequisites:

- Windows Powershell 1.0
- .NET Framework 3.5 Service Pack 1
- IIS (Internet Information Services
- ASP.NET 2.0
- COM+ components

After this is all done, we can install Microsoft SQL 2005 server for the SCOM database.*
*(Note! When you have more than ten SCOM agents, it’s recommended that you install a dedicated Microsoft SQL 2005 server)

Now Microsoft SQL 2005 server SP2 is installed succesfully, we’re going to prepare our Active Directory for Microsoft System Center Operations Manager 2007.

Create two new user account in your Active Directory. These users can be used for the following tasks:
(OpsMgr-SAA, Server Action Account) to gather operational data from providers, to run responses, and to perform actions such as installing and uninstalling agents on managed comptuers.
Make this user member of the Domain Admins Security Group.
(OpsMgr-SDK, SC Database Server) to logon to the System Center Database Server.
Make this user member of the Local Adminstrators Security Group on the SCOM SQL server*
*(Note! in this example not nessecary because there’s only one server for all the services.)

Create also a Security Group in your Active Directory for managing the System Center Operations Manager Environment.
(OpsMgr-Admins, for managing the SCOM environment)
This group has full permissions to manage within a Management Group.

Now we can install System Center Operations Manager.

 The continuous availability architecture built into Exchange 2010 provides new benefits for organizations and their messaging administrators:

• Multiple server roles can co-exist on servers that provide high availability. This enables small organizations to deploy a two-server configuration provides full redundancy of mailbox data, while also providing redundant Client Access and Hub Transport services.
• An administrator no longer needs to build a failover cluster in order to achieve high availability. Failover clusters are now created by Exchange 2010 in a way that is invisible to the administrator. Unlike previous versions of Exchange clusters which used an Exchange-provided cluster resource DLL named ExRes.dll, Exchange 2010 no longer needs or uses a cluster resource DLL. Exchange 2010 uses only a small portion of the failover cluster components, namely, its heartbeat capabilities and the cluster database, in order to provide database mobility.
• Administrators can add high availability to their Exchange 2010 environment after Exchange has been deployed, without having to uninstall Exchange and then re-deploy in a highly availability configuration.
• Exchange 2010 provides a view of the event stream that combines the events from the operating system with the events from Exchange.
• Because storage group objects no longer exist in Exchange 2010, and because mailbox databases are portable across all Exchange 2010 Mailbox servers, it is very easy to move databases when needed.

Get-Mailbox | Where {$_.HiddenFromAddressListsEnabled -eq $true} | ft -wrap

Get-Mailbox | Where {$_.HiddenFromAddressListsEnabled -eq $true} | Select Name, HiddenFromAddresslistsEnabled, ExchangeVersion

Download Details: Microsoft Exchange Server 2010 Beta
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1898ed2c-2f88-48ac-824e-d3d20fad77d7

TechNet: Microsoft Exchange Server 2010 (Beta)
http://technet.microsoft.com/en-us/library/bb124558(EXCHG.140).aspx

Today i’ve installed the public beta release and here are some first looks of Microsoft Exchange Server 2010. (Exchange 14)

First of all i’ve installed a Microsoft Windows 2008 x64 Server. The next step is to install the pre-requisites.

- Microsoft .NET Framework 3.5
- Windows Remote Management (WinRM) 2.0 CTP 3
- Windows PowerShell 2.0 CTP 3
- Update from KB 951725
- Update from KB 950888
- Update from KB 951116
- Update from KB 952664
- Update from KB 953290
- Update from KB 958178
- ASP.NET AJAX 1.0 Extensions

ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
ServerManagerCmd -i NET-HTTP-Activation
ServerManagerCmd -I RPC-over-HTTP-proxy
ServerManagerCmd -i RSAT-ADDS (reboot required)

After installing this pre-requisites, we’re going to install Microsoft Exchange 2010.

Database Portability cuts disaster recovery restore time:

1) Run eseutil /r <Enn> to commit all logs and put database into clean shutdown state.
<Enn> specifies the log file prefix for the storage group that contains the database into which you intend to replay the log files. The log file prefix specified by <Enn> is a required parameter for Eseutil /r. You can run the following Exchange Management Shell command to determine the log file prefix of a storage group:
Get-StorageGroup <Server_Name>\<StorageGroup_Name> | fl LogFilePrefix

2) Select a storage group on the replacement server and create the required database.
(Note: make sure the Storage Group and the Database have the same name as previous configuration on the crashed server).
3) Enable: EMC > Server Configuration > Mailbox > Database Management > Properties > General > This database can be over written by restore. Or: Set-MailboxDatabase <Database Name> -AllowFileRestore:$true.
4) Move database files (edb & log files, Exchange Search catalog) to appropriate location on new server.
5) Mount database.
6) Run Move-Mailbox -ConfigurationOnly — so accounts in AD will point to mailboxes on the replacement machine.
Get-Mailbox -Database <SourceDatabase> |where {$_.ObjectClass -NotMatch ‘(SystemAttendantMailbox|ExOleDbSystemMailbox)’}| Move-Mailbox -ConfigurationOnly -TargetDatabase <TargetDatabase>

After replication completes, when Outlook clients try to connect to their mail, the Autodiscover service will automatically redirect them to its new location.

1) Open the commandline
2) Type in eseutil /?
3) Choose the right switch

———————————————————————–
Checking your database integrity: (Note: make sure you’ve dismounted your database(s)!! )
eseutil /g “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPINTEG.edb”

eseutil /g: tool with the check integrity option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPINTEG.edb”: location of the temperary database file

       
———————————————————————–

Repairing a corrupted or damaged database:  (Note: make sure you’ve dismounted your database(s)!! )
eseutil /p “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPREPAIR.edb”

eseutil /p: tool with the repair option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPREPAIR.edb”: location of the temperary database file

       
———————————————————————–

Offline defragmentation of a database:  (Note: make sure you’ve dismounted your database(s)!! )
eseutil /d “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPDEFRAG.edb”

eseutil /d: tool with the offline defragmentation option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPDEFRAG.edb”: location of the temperary database file

   
———————————————————————–

First of all we are gonna export the user mailboxes with ExMerge, after the export, we are gonna import the mailboxes with PowerShell. You can follow this article to provide the migration step by step.

I’ve installed an Microsoft Exchange 2003 Enterprise SP2 environment with 10 user mailboxes. I’ve also installed a Microsoft Windows XP workstation with Microsoft Office 2007.

The allias of the user is the same as the User Logon Name.

By default, the Administrators, Domain Admins and Enterprise Admins have deny permissions on the Information Store. Make sure you configure the right permissions, so you have access to the mailboxes for making the export with ExMerge.

1) right-click on your Exchange Server, choose Properties
2) go to the Security tab, hit Administrators (also do this for Domain Admins and Enterprise Admins)
3) Advanced, hit Allow inheritable….Copy
4) hit Administrators, allow Send As and Receive As (also do this for Domain Admins and Enterprise Admins)
5) Restart the Microsoft Exchange System Attendant service.

Configure an MAPI profile for a user and generate some e-mail traffic. (e-mail, calendar items, tasks etc..)

Now we’re gonna export the user mailboxes with ExMerge.

        

In the next post, we’re gonna import the user mailboxes into the new Microsoft Exchange 2007 SP1 environment using PowerShell.

Open the WinPE Command Prompt by Clicking Start -> All Programs -> Microsoft Windows AIK -> Windows PE Tools Command Prompt.

Create an empty folder which you will use to mount the WinPE image:

mkdir D:\mount

Locate your WinPE boot image. For example:
D:\RemoteInstall\Boot\LiteTouchPE_x86.wim

Mount the image using the following command, substituting your own mount path and WinPE image.  (Note: each WIM file can contain multiple images, use the imagex /info command to locate the correct number for your boot image)
imagex /mountrw D:\RemoteInstall\Boot\LiteTouchPE_x86.wim 1 D:\mount

Locate the INF file for your network driver. Use the following command to inject the driver, subsituting your own driver INF and mount path.
peimg /inf=D:\<driverpath>\<driver>.INF /image=D:\mount

Commit the changes to the image.
imagex /unmount /commit D:\mount

Make sure you’ve a copy of the orriginal WIM file, so you can always replace a backup of this file.

As noted in previous posts, Exchange 2007 updates are cumulative and release-specific. This roll-up is for Exchange 2007 SP1, and supersedes all previous update roll-ups for Exchange 2007 SP1.

Update Roll-up 7 for Exchange Server 2007 SP1 has 50 fixes, including important fixes for SCR and IMAP4 issues.

Fixes for the following issues are included (details in KB960384):
946449 A non-read report message is sent after you perform a “Mark All as Read” operation against unread e-mail messages in Exchange Server 2007

949113 Unexpected modified instances of a recurring meeting may appear when you use Entourage to access a calendar on a computer that is running Exchange Server 2007

949114 Duplicate calendar items may appear when you use Entourage to access a calendar on an Exchange 2007 server

949464 The customized properties are removed in the recipients’ calendars when you send a meeting request that includes customized properties

950115 When a CDO 1.2.1-based application generates a meeting request that includes some European characters in the message body, these characters appear as question marks in Exchange 2007

951341 Users cannot read calendar items when they connect Exchange Server 2007 by using certain IMAP4 or POP3 clients

952778 Event ID 9874 is frequently logged on Exchange Server 2007 with Service Pack 1

953094 The value in the “Messages queued for submission” performance counter on the mailbox role of Exchange Server 2007 increases after a meeting request is delivered

954213 All Test commands that are related to the Client Access Server fail when you run the commands on an Exchange 2007 server in a disjoint namespace

954741 The UseRUSServer parameter does not work if an administrator has specified an RUS server on a target mailbox server

954898 The LegacyExchangeDN attributes for mail-enabled objects are incorrectly set in an environment that contains Exchange 2003 and Exchange 2007

955027 The Edgetransport.exe process may crash on a hub transport server that is running Exchange Server 2007 Service Pack 1

955462 You notice high CPU usage when the IMAP service is running on an Exchange 2007 Service Pack 1 server that has the CAS role

955778 You receive a Non-Delivery Report (NDR) message when you send an e-mail message to a non-SMTP address in an Outlook client that is using Cached mode

956069 A Non-Delivery Report (NDR) is generated when an Exchange Server 2007 user tries to send a message to a recipient who has a one-off FAX address that includes any characters that are larger than 0xFF in Unicode

956205 Corrupted characters appear in the Subject field or in the Location field of a recurring calendar item after a user adds DBCS characters to a field in a meeting occurrence by using an Outlook 2002 client

956275 An Exchange 2007 sender’s address is split into two separate addresses when an external recipient replies to the message

956455 The display name appears in a received message even though the property of the user mailbox is set to “Hide from Exchange address lists” in Exchange Server 2007

956687 Messages stay in the submission queue after you enable per-mailbox database journaling in an Exchange Server 2003 and Exchange Server 2007 coexisting environment

957019 Images cannot be pasted in an Exchange Server 2007 Outlook Web Access message body

957071 The MSExchange Transport service may crash intermittently on the Exchange 2007 server

957124 You do not receive an NDR message even though your meeting request cannot be sent successfully to a recipient

957227 The Exchange Management Console crashes when one or more domain controllers of a top-level domain are not reachable

957485 The Test-OwaConnectivity command returns a warning message in Exchange Server 2007 when there is a disjoint namespace

957504 The IMAP4 service crashes intermittently, and Event ID 4999 is logged on Exchange Server 2007

957683 An IP Gateway can still be used to dial out for a “Play on Phone” request after the IP Gateway is disabled

957834 Network shares are deleted and created intermittently by the replication service on an Exchange SCC cluster when SCR is enabled on the Exchange server

957947 The Exchange Information Store service may crash when an Entourage client synchronizes with an Exchange 2007 server

958091 You cannot update the task complete percentage to any value other than 0 or 100 in Outlook Web Access

958093 Voice mail messages are not stamped with the disclaimer that is defined in the transport rule in an Exchange Server 2007 environment

958128 Replication messages stay in a queue in a retry state after a public folder database is dismounted

958331 The Restore-StorageGroupCopy command may fail in an Exchange Server 2007 SCR environment

958444 Event 522 is logged when replication is resumed on a suspended Storage Group on an Exchange Server 2007 CCR or SCR environment

958472 An unexpected text string appears at the top of the message body when an Exchange Server 2007 user sends an HTML message by using Outlook Web Access

958552 The ByteEncoderTypeFor7BitCharsets setting does not take effect for the US ASCII character set after you install the hotfix that is mentioned in Microsoft Knowledge Base article 946641

958638 Exchange 2007 Server cannot parse X-Priority headers from clients that submit X-Priority headers that contain additional comments

958803 The EdgeTransport.exe process may stop responding in Exchange Server 2007 when the priority queuing feature is enabled

958872 The Map This Address feature in the contact page for an OWA client does not work in Exchange Server 2007

959100 Exchange Server 2007 cannot route e-mail messages to mail enabled Non-MAPI public folders that are hosted on an Exchange Server 2003 server

959135 Event 9673 occurs when the Microsoft Exchange Information Store service crashes on a computer that is running Exchange 2007 with Service Pack 1

959397 An increase in database size is generated unexpectedly when IMAP4 users use a Copy command in Exchange 2007

959434 The last logon time is not updated to reflect the logon times that have occurred after users log on to their mailboxes by using the Entourage client in an Exchange 2007 environment

959545 A redirection message in Outlook Web Access 2007 is incorrect when the message is translated to Korean

959671 The Manage Mobile Devices option is not displayed in Exchange Management Console after a mobile device re-synchronizes with an Exchange 2007 server

959952 The Set-Mailbox command does not change the AutomateProcessing attribute for an Exchange Server 2007 user when a regular user mailbox is converted from a room mailbox

960291 Outlook Web Access or an Exchange Web Service application does not correctly display a monthly or yearly recurring appointment or meeting request

960292 The MSExchangeIMAP4 service may crash intermittently after you apply an update rollup for Exchange Server 2007 Service Pack 1

960349 The Exchange Information Store service may crash after you enable tracing for the logon actions

961281 An error is returned when you enable SCR from any source in a child domain after you install Exchange Server 2007 Service Pack 1 Rollup 5

961395 The Exchange 2007 Unified Messaging server does not update the caller information if an external user makes a call

RES Workspace Extender is a very usefull feature to enable applications not suitable for Server Based Computing (SBC) environments to integrate seamlessly into these environments anyway. You may already be familiar with the concept of Seamless Windows. This was an idea developed by Citrix back in the Metaframe days, to enable the client to spoof an remotely published app, running off a citrix box, to look like it was integrated into the local desktop. What the RES Workspace Extender does, is quite the opposite, hence the reverse reference: It makes a local application look like it’s part of a remote desktop, hence effectively turning a PC into a thin client with fat-client capabilities.

So let’s see the screenshots, so you can see the tool running in a live environment.

In my case the name of the terminal server is SRV-TRM01. As you can see, the application Winrar(for example, you can also use Windows Media Player or a CD/DVD burning application) is not installed on the terminal server. So let’s publish this application with RES Powerfuse using the tool RES Workspace Extender. I’ve installed a workstation called WS-XP01. I’ve installed the RES Workspace Extender and Winrar. You can see the RES Workspace Extender running in the system tray of the workstation.

The next step is to open the RES Powerfuse Management Console. Add a new application.

Make sure you enable the option Run as Workspace Extension (Yellow text). So let’s logon to the Terminal Server and as you can see there is our published application Winrar. When you start the application, and you take a look at the Windows Task Manager on the Terminal Server, you can see that there’s no proccess called winrar.exe, exactly that’s because the application is running local on your workstation!

The same for example Windows Media Player. As you can see, there’s no proccess called wmplayer.exe.

You can also see the difference between running Windows Media Player local or on the Terminal Server…so what is your choice??

I’ve configured a second virtual hard disk for the Hyper-V Server, so lets make it available for storing my new virtual machines.

1) Open Management Console on the Management Server. (Start, Run, MMC)
2 ) Add/Remove snap-in, Disk Management
3) The following computer: 172.16.1.200
4) Create a new partition
5) Check if the new disk is succesfully created

Before you’re going to manage the Hyper-V Server, you must install a feature.

1) Open the Server Manager
2 ) Features, Add features
3) Remote Server Administration Tools
4) Role Administration Tools
5) Hyper-V Tools

Now we are going to connect to the Hyper-V Server.1) Open the Hyper-V Manager
2) Right-click on Microsoft Hyper-V Servers
3) Connect to Server
4) Another Computer, 172.16.1.200

After connecting to the Hyper-V Server, I’ve get the following error:
“The Msvm_VirtualSystemManagementService object was not found”The solution for this error is installing the following update:
Hyper-V Update for Windows Server 2008 x64 Edition (KB950050)

For a list of all the available updates for Hyper-V Server, you can browse the following link.
http://technet.microsoft.com/en-us/library/cc753637.aspx

The next step is to configure the Hyper-V Server Settings.

1) Right-click on your Hyper-V Server
2) Hyper-V Settings
3) Choose a location for Virtual Hard Disks, in my environment the new partition we’ve made E:\VM\VHD
4) Choose a location for Virtual Machines, in my environment the new partition we’ve made E:\VM\VMI’ve copied a Microsoft Windows XP Professional ISO to E:\ISO on the Hyper-V Server. Let’s install a new Virtual Machine

1) Right-click on your Hyper-V Server
2) New, Virtual Machine
3) Give the name for the new VM and the location (default E:\VM\VM)
4) Configure the Memory for the new VM
5) Configure the network connection (you can choose between, External, Internal or Private)
6) Give the name for the VHD file and the size of it.
7) Give the installation source. In my case it’s the ISO file I’ve copied to E:\ISO
Finisch the wizard and start the new VM

The new machine is created now. The next post I’ll go further with installing and tuning the new VM.

Hive: HKEY_CURRENT_USER
Key: Control Panel\Desktop
Name: ScreenSaveTimeOut
Type: REG_SZ
Value: 3600
(default is 600, 10 minutes)

Hive: HKEY_LOCAL_MACHINE
Key: SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Name: AutoAdminLogon
Type: REG_SZ
Value: 1 enable auto logon
Value: 0 disable auto logon

Hive: HKEY_LOCAL_MACHINE
Key: SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Name: DefaultUserName
Type: REG_SZ
Value: account to logon automatically (for example: Administrator)

Remember, by default, message tracking is enabled on all Exchange 2007 computers that have the Hub Transport, Mailbox, or Edge Transport server roles installed.

You can enable or disable the message tracking performing the following steps:

1) Open the Exchange Management Console
2) Open Server Configuration, Hub Transport, Properties on your servername
3) Click on the tab Log Settings       

You can also configure the message tracking with the Exchange Management Shell. You can use the following command:

Set-TransportServer <Identity> -MessageTrackingLogEnabled <$true | $false>
(For example: Set-TransportServer SRVEXC01 -MessageTrackingLogEnabled $true)
——————————————————————

By default, the place of your message tracking logfiles is the following location:
DriveLetter:\Exchsvr\TransportRoles\Logs\MessageTracking
(For example: E:\Exchsvr\TransportRoles\Logs\MessageTracking)

You can change this path with the Exchange Management Console, just browse to the new folder, or you can change this path with the Exchange Management Shell with the following command:
Set-TransportServer <Identity> -MessageTrackingLogPath <LocalFilePath>
(For example: Set-TransportServer SRVEXC01 -MessageTrackingLogPath E:\MessageTracking\Logs)

Note! when you change the message tracking logpath, make sure this folder has the following permissions:
- Administrator: Full Control
- System: Full Control
- Network Service: Read, Write, and Delete Subfolders and Files
——————————————————————

By default, the maximum size for each message tracking log file is 10 MB. When a message tracking log file reaches its maximum size, Exchange 2007 opens a new message tracking log file. This process continues until either of the following conditions is true:
- The message tracking log directory reaches its specified maximum size.
- A message tracking log file reaches its specified maximum age.

After the maximum size or age limit is reached, circular logging deletes the oldest message tracking log files.
By default, the maximum size for the whole message tracking log directory is 250 MB. Circular logging deletes the oldest message tracking log files when either of the following conditions is true:
- A message tracking log file reaches its specified maximum age.
- The message tracking log directory reaches its specified maximum size.You can change this size with the following command:
Set-MailboxServer <Identity> -MessageTrackingLogMaxDirectorySize <DirectorySize>
(For example: Set-TransportServer SRVEXC01 -MessageTrackingLogMaxDirectorySize 600MB)
——————————————————————

By default, the maximum age for any message tracking log file is 30 days. Circular logging deletes the oldest message tracking log files if either of the following conditions is true:
- The message tracking log directory reaches its specified maximum size.
- A message tracking log file reaches its specified maximum age.You can change this age with the following command:
Set-TransportServer <Identity> -MessageTrackingLogMaxAge <Age>
(For example: Set-TransportServer SRVEXC01 -MessageTrackingLogMaxAge 90.00:00:00)

 To specify an age value, enter it as a time span, as follows: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. The valid input range for this parameter is 00:00:00 to 24855.03:14:07. Setting the value of the MessageTrackingLogMaxAge parameter to 00:00:00 prevents the automatic removal of message tracking log of files because of their age.
——————————————————————

To see all the settings of your TransportServer, you can use the following command:
get-transportserver | fl

In the next post I’ll let you see how to use the Exchange Message Tracking for easy tracing some e-mailtraffic.

Everything looks fine, but there was a problem with Adobe Reader 9.0. The application wasn’t able to start and I received a EventID 1000 in the event viewer of my Terminal Servers.

—————————————————-
 ”Faulting application AcroRd32.exe, version 9.0.0.332, time stamp 0×4850f0a3, faulting module Annots.api, version 9.0.0.332, time stamp 0×4850e57f, exception code 0xc0000005, fault offset 0×001bd9e0, process id 0xb9c, application start time 0×01c99438e39a6ea2.”
—————————————————- 

So I started to trouble shoot and I found the following solution. This action must be configured on every Terminal Server.

Set the compatibility mode of AcroRd32.exe to Windows XP (Service Pack 2). After this modification, everything works fine!

1) Browse the executable AcroRd32.exe on your Terminal Servers
2) Right-click on the executable and choose properties
3) Go to the Compatibility tab
4) Choose Show settings for all users
5) Enable the compatibility mode Windows XP (Service Pack 2)

You can start the customization tool with the following command.
setup.exe /admin

After you’ve finished making your settings, you can save this file in the Updates folder of your installation source on the network. Microsoft Office will now be installed using your custom installation file.

These are some configurations that you can make in the wizard:

- Organization information
- Licensing and user interface
- Office security settings
- Setup properties
- User settings
- feature installation states
- Profile settings
- Exchange server settings

Update Rollup 6 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

950675  Downloaded .xls file attachments are empty when you open the files by using Outlook Web Access on Exchange Server 2007 Service Pack 1

955443  Some free/busy messages are not replicated from Exchange 2007 to Exchange 2003 servers after some mailboxes are migrated from Exchange Server 2003 to Exchange Server 2007

956536  The Microsoft Exchange File Distribution service uses lots of memory and processor time when Exchange Server 2007 processes many OABs

956624  The Microsoft Exchange Transport service crashes continuously after you enable journal rule or deploy an antivirus application on an Exchange Server 2007 server

957748  The custom message class of contact object is overwritten by the normal IPM.Contact class when an Exchange 2007 server replicates the contact object to any other public store

959239  MS09-003: Vulnerabilities in Microsoft Exchange could allow remote code execution

More information you can find here. You can download Rollup 6 for Exchange 2007 SP1 here.

In my testenvironment I’ve created 50 test user objects and deleted a couple of this user objects. Now we are going to restore the objects. First I’ve downloaded the following commandline tool adrestore. This tool I’ll using for the restore.

The following commands can be used:

adrestore 
This command will give you an overview of all the tombstoned objects in your Active DirectoryThis command asks for an conformation to restore all the individual tombstoned objects.

adrestore -r

adrestore -r “CN of the tombstoned object”, for example adrestore -r testuser11
This command perform a restore of tombstoned object testuser11

Note: after performing a restore of the tombstoned objects, the accounts are disabled and the user must change password at next logon. Before you can enable this account, make sure you reset the password that meets your password policies, configured in your Default Domain policy.

• Network infrastructure
• Directory services, identity management, and authentication 
• Security policies
• Business continuity (disaster recovery, personnel, equipment, and data)
• Design of IT administrative structure (delegation models)
• Best practices, standards, and service level agreements (SLAs)

This was also the last certificate for Windows Server 2008. The next few months I’am going to start with SCOM, TS: Microsoft System Center Operations Manager 2007, Configuring

TCP port 25 – SMTP
TCP port 26 – SSL secured SMTP
TCP port 110 – Post Office Protocol (POP3)
TCP port 995 – SSL secured POP3
TCP port 143 – Internet Message Access Protocol v. 4 (IMAP4)
TCP port 993 – SSL secured IMAP4
TCP port 80 – HTTP for Outlook Web Access
TCP port 443 – SSL secured HTTP for Outlook Web Access (HTTPS)
TCP/UDP port 389 – Lightweight Directory Access Protocol (LDAP)
TCP port 3268 – LDAP communications with an Active Directory Global Catalog Server
TCP port 119 – Network News Transfer Protocol (NNTP)
TCP port 563 – SSL secured NNTP
TCP port 135 – Remote Procedure Protocol (RPC) however it will also use ports 1024 and up as needed.
TCP/UDP port 53 – Domain Name System (DNS)
TCP port 102 – Mail Transfer Agent (MTA) *Only used in X.400 connections.
TCP/UDP port 88 – Kerberos

First off all i’ve installed a Windows 2003 Server with HP Data Protector 6.0. (Note: if you’re using Exchange 2007, install patch DPWIN_307 or later)

After the installation we’re are going to deploy the HP Client to the Exchange 2007 server, for communicating with the Backup server.

The next step is configuring the device for the backup destination. In my situation it’s a backup to disk.

Now the device is created, we can go further with configuring the Exchange full Store backup.

In the next few days i’m going to configure the Exchange 2007 Single Mailbox backup.

- Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess key.
- Create the “CacheTTLUser” value
- Right-click MSExchange ADAccess, select New, and then select Key.
- Name the new key Instance0.
- Right-click Instance0, select New, and then select DWORD value.
- Name the new DWORD value “CacheTTLUser”.
- Right-click CacheTTLUser, and then click Modify.
- Enter a decimal value of 300 (5 minutes)

Alternately, copy this text file and paste it into a file called MailboxCache.reg, then import it into the registry of each of your Exchange 2007 Mailbox servers

———————————————————————-
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem]
“Reread Logon Quotas Interval”
=dword:000004b0
“Mailbox Cache Age Limit”
=dword:00000014
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess\Instance0]
“CacheTTLUser”
=dword:0000012cc
———————————————————————-

In this script I use the command line tool dsadd.

dsadd user “CN=Testuser01,OU=Gebruikers,DC=testlab,DC=local” -upn testuser01@testlab.local -fn testuser01 -pwd P@$$W@rd
dsadd user “CN=Testuser02,OU=Gebruikers,DC=testlab,DC=local” -upn testuser02@testlab.local -fn testuser02 -pwd P@$$W@rd
dsadd user “CN=Testuser03,OU=Gebruikers,DC=testlab,DC=local” -upn testuser03@testlab.local -fn testuser03 -pwd P@$$W@rd
dsadd user “CN=Testuser04,OU=Gebruikers,DC=testlab,DC=local” -upn testuser04@testlab.local -fn testuser04 -pwd P@$$W@rd
dsadd user “CN=Testuser05,OU=Gebruikers,DC=testlab,DC=local” -upn testuser05@testlab.local -fn testuser05 -pwd P@$$W@rd

To be continued…

Get-Mailbox | Get-mailboxpermission | where {-not ($_.User -like “NT AUTHORITY\SELF”)} | Ft -wrap

When you want the full access permissions configured on one specific mailbox, you can add the -identity switch. For example:

Get-Mailbox -identity systeembeheer | Get-mailboxpermission | where {-not ($_.User -like “NT AUTHORITY\SELF”)} | Ft -wrap

Get-Mailbox | Get-ADPermission | where {($_.ExtendedRights -like “*Send-As*”) -and -not ($_.User -like “NT AUTHORITY\SELF”)} | Ft -wrap

When you want the Send-As permissions configured on one specific mailbox, you can add the -identity switch. For example:

Get-Mailbox -identity systeembeheer | Get-ADPermission | where {($_.ExtendedRights -like “*Send-As*”) -and -not ($_.User -like “NT AUTHORITY\SELF”)} | Ft -wrap

The Windows 2003 Domain Controller is configured with a domain upgrade.local, forest functional level is Windows Server 2003 and the domain functional level is Windows Server 2003. This server is also the DNS server for this domain. There’s is one forward lookup zone and I’ve created a reverse lookup zone for the 172.16.10.x Subnet. We’re going to migrate to Windows 2008 Server.

First of all, I’ve installed a second virtual server with Windows 2008 Server and give it a static IP address, a subnet mask and a DNS server.

Now you have to prepare the forest and the domain with the new schema extensions.

D:\sources\adprep\adprep/forestprep and D:\sources\adprep\adprep /domainprep.
(Note: if you want to add a RODC, Read Only Domain Controller, you’ve to run also the following command: adprep /rodcprep. There must be already a Windows 2008 Domain Controller present in the domain before you can add a RODC.)

Now you can run a DCPROMO on the Windows 2008 Server.

The new Windows 2008 Domain Controller is succelfully promoted in the existing domain upgrade.local.

The next step is to move all the FSMO roles to the new Domain Controller. The following settings must be made.

Change the Domain Naming Master Active Directory Domains and Trusts, Operations Master, Change

Change the Schema Master run the following command regsvr32 schmmgmt.dll , now you’re able to add the Schema Snap-in in your Management Console.
Active Directory Schema, Operations Master, Change

   

Change the RID Master, PDC Emulator and the Infrastructure Master Active Directory Users and Computer, Your domain, Operations Masters, Change

Now all the FSMO roles are transfered to the new Server 2008 Domain Controller. Now we can demote the Windows 2003 Domain Controller by running the DCPROMO command.

After this steps and a copple of reboots, the migration is done! You now have a Windows 2008 Domain Controller.

First i’ve build an clean Windows 2003 x64 Server and promoted the server to a new domain controller of upgrade.local.
(note: if you want to upgrade your Windows 2000 Domain Controller to Windows 2008, you’ve first have to do an in-place upgrade to Windows 2003!)

Note: make sure you’ve at least 14000 Mb (14 Gb) free space available on your system partition.

Now place the Windows 2008 DVD in your computer, or mount it in your virtual environment.

Browse to your DVD player (in my environment it’s D:) and go to the following folder D:\sources\adprep.

First we’re going to prepare our forest with the following command: adprep /forestprep. After this command, we’re going to prepare our domain: adprep /domainprep.

With the following steps, you can extend your VMDK file.

- Open the commandline (Start, Run, CMD)
- Browe to the vmware-vdiskmanager.exe
- Give the new size of the VMDK file with the parameter -x
- Browse to the VMDK file you want to extend

So, for example, the full command would be:
C:\Program Files (x86)\VMware\VMware Workstation>vmware-vdiskmanager.exe -x 40Gb D:\VM\INPLACEUPGRADE\INPLACEUPGRADE.vmdk
(Note: after the parameter X, give the total new size of the VMDK file. So when your VMDK was 10 Gb, you want to extend with 30 Gb, you type in 40 Gb)

The next step is to make the system partition bigger. I’ll use Gparted Live. Mount the ISO, boot from it, and within three steps the partition grown to 40 Gb.