This is a bug in Windows 7 
http://support.microsoft.com/kb/947222

Solution:

Do not grant the Read permission to the administrator for the Desktop.ini files on the server. To do this, follow these steps:

Note If more than one Desktop.ini file exists, follow these steps for all the Desktop.ini files.

1. Right-click the Desktop.ini file, click Properties, and then click the Security tab.
2. In the Group or user names pane, click Administrators.
3. Click to select the Deny check box for the Read permission.
4. Click OK.

If you have 1000+ home folders this is not great thing to do

Richard Willis created a nice powershell script that will do it for you
You need only change the groupName to the group that you will give deny read permissions.
Save the script in de home folder where all the “My Documents” are and run the script.

The Script:
———————————————————————————————————–

$folders = Get-ChildItem | where-object {$_.psiscontainer};
foreach ($folder in $folders)
{
$desktopIni = Get-ChildItem $folder -Filter desktop.ini -Force
if ($desktopIni -ne $null)
{
$Acl = Get-Acl $desktopIni.FullName
$Ar = New-Object system.security.accesscontrol.filesystemaccessrule `
("groupName","Read","Deny")
$Acl.SetAccessRule($Ar)
Set-Acl $desktopIni.FullName $Acl
}
}

———————————————————————————————————-

Before the rollup 1 they were previously multipart/alternative messages with both text/plain and text/html subparts.

Solution:
You can set in through in the GUI or using Powershell to set the value to 0 text only

ImapMessagesRetrievalMimeFormat:
0:Text Only
1:HTML Only
2:HTML and Alternative Text
3:Enriched Text Only
4:Enriched Text and Alternative Text
5:Best Body Format

Exchange Management Console:

1. In the console tree, expand Server Configuration, and then click Client Access.

2. In the work pane, click the POP3 and IMAP4 tab.

3. In the work pane, select IMAP4 and then, in the result pane, click Properties.

4. On the IMAP4 Properties page, click the Retrieval Settings tab.

5. In the Message Retrieval pane, select a message format from the drop-down list under Message MIME format. I choies for 0

6. Click Apply, and then click OK to save your changes.

Powershell:

Set-CASMailbox -Identity yourcasserverhere -PopMessagesRetrievalMimeFormat 0

If you want a list with al the pda’s that are connected to your Exchange Organization.

You can use the following Powershell command let.
Get-Mailbox –resultsize unlimited | Get-ActiveSyncDevice | fl userdisplayname,DeviceModel,Devicetype, DeviceUserAgent > c:\pdas.txt

Some of the hotfixes would have been rolled up in a Windows update or service pack. Given that the Exchange team released SP1 earlier than what was planned and announced earlier, it did not align with some of the work with the Windows platform. As a result, some hotfixes are available from MSDN/Connect, and some require that you request them online using the links in the corresponding KBs. All these updates may become available on the Download Center, and also through Windows Update.

These hotfixes have been tested extensively as part of Exchange 2010 SP1 deployments within Microsoft and by our TAP customers. They are fully supported by Microsoft.

The TechNet article Exchange 2010 Prerequisites is updated with the hotfixes and install the prerequisites required for your server version (the hotfixes are linked to in the above table).

You can use the Install the Windows Server 2008 SP2 operating system prerequisites on a Windows 2008 R2 server. Only you have to run the following powershell command: Import-Module ServerManager

Installed Exchange 2010 SP1 on a Windows 2008 R2 Server with problems. I feels that the MMC is faster. Tomorrow upgrading a DAG/NLB cluster to Exchange 2010 SP1.

Well, let us first list the directories that are used in the Exchange web service:

EWS is used for OOF, Scheduling assistance and free+busy Lookup.
OAB provides offline address book download services for client.
Autodiscover is used to provide users with autodiscover service.
EAS provides ActiveSync services to Windows Mobile based devices.
OWA provides outlook web access for users.
ECP provides Exchange control panel feature for Exchange 2010 users only.

Issues that might be resolved using the troubleshooting steps here:

You cannot set the OOF using outlook client, you receive the server not available error.
You cannot view free/busy information for other users.
You cannot use scheduling assistance, also you might receive not free/busy information data retrieved.
You cannot download Offline Address book errors.
You cannot use autodiscover externally.
Certificate mismatch error in autodiscover, users prompted to trust certificate in outlook 2007/2010.

First let us start by settings the right virtual directory configuration required for Exchange 2010 to work correctly:
Configure External and Internal URLs for OWS, ref: http://technet.microsoft.com/en-us/library/bb310763.aspx

You have to configure the internal URL to be the server name. In case you have multiple cas/hub servers configured in a NLB then can use the nlb cluster name for the internal url. 
External URL will be the URL used by users to access webmail e.g. https://webmail.wardvissers.nl/owa 

Configure the autodiscover internal URL, ref: http://technet.microsoft.com/en-us/library/bb201695.aspx

You will use the powershell cmdlet : Set-ClientAccessServer –Identity <CAS Server Name> -AutoDiscoverServiceInternalUri: <Internal URL>, this FQDN must match the URL included in the certificate. If you have NLB cluster then you put the internal name here like nlbek10.wardvissers.local

If you cannot use autodiscover.wardvissers.nl internally (you have a domain name of domain.local and you must use it), you will get a certificate miss match error, you will have to include the internal name in the SAN certificate if you purchase an external SAN certificate. 

You cannot set autodiscover external URL since outlook will try to access https://autodiscover.wardvissers.nl/autodiscover/autodiscover.xml, this behavior is by design and cannot be changed.

Best Practice: Use SAN Certificates

Depending on how you configure the service names in your Exchange deployment, your Exchange server may require a certificate that can represent multiple domain names. Although a wildcard certificate, such as one for *.wardvissers.nl, can resolve this problem, many customers are uncomfortable with the security implications of maintaining a certificate that can be used for any sub-domain. A more secure alternative is to list each of the required domains as SANs in the certificate. By default, this approach is used when certificate requests are generated by Exchange.

Best Practice: Use the Exchange Certificate Wizard to Request Certificates

There are many services in Exchange that use certificates. A common error when requesting certificates is to make the request without including the correct set of service names. The certificate request wizard in the Exchange Management Console will help you include the correct list of names in the certificate request. The wizard lets you specify which services the certificate has to work with and, based on the services selected, includes the names that you must have in the certificate so that it can be used with those services. Run the certificate wizard when you’ve deployed your initial set of Exchange 2010 servers and determined which host names to use for the different services for your deployment.

Which Names you must include when you use a third party SAN certificate, ref http://technet.microsoft.com/en-us/library/dd351044.aspx:
External:
webmail.wardvissers.nl
autodiscover.wardvissers.nl
legacy.wardvissers.nl (If you migrating from 2003 to 2010)
Internal:
autodiscover.wardvissers.local
legacy.wardvissers.local
nlbek10.wardvissers.local(Internal NLB CAS/HUB Cluster)
casarray.wardvissers.local(I use this address for the casarray. It has the same ip as the nlbek10)

Microsoft Deployment Toolkit 2010 has some nice improvements to handle drivers. I will describe how I like to manage drivers in MDT 2010.

Some time I wrote i article about how to get the Name & Model from a computer. This is very important when you want to import only the right drivers automatically.

First we have to build the ‘Out-of-Box Drivers’ folder structure and import drivers. I have subdirectories for each architecture, brand and model.  This is what my folder tree looks like:

However, you can build your own structure, as long as you respect the proper model & brand (make) name of the vendors.

Build Out-of-Box Drivers tree

To build up the folder structure you have to know the model name of your hardware. To retrieve the proper computer name execute at powershell command prompt: ‘Get-WmiObject -Class win32_computersystemproduct | fl Name,Model,UUID,Identifyingnumber,Vendor’, to get the exact name WMI queries to determine the computer model. In my case the computer name is “Latitude D830”.

Now that we have drivers imported in our Deployment Share, it’s time to move on.

1. DriverGroups

DriverGroups existed in MDT 2008 already, although the MDT Team added subdirectory support in MDT 2010.

At deployment phase MDT uses WMI to query the proper computer model and only the current model drivers will be injected. In order to get this working properly, you have to use the EXACT model name in your Out-of-Box Driver tree.

Inject the correct drivers in your Task Sequence

Add a new step in your Task Sequence to inject the correct drivers. MDT will query the computer name and inject the drivers which corresponds with the computer name from the Out-of-Box folder structure, right before applying the image at deployment.

I use ‘DriverGroup_001’ as Task Sequence Variable, and Win7×64\%Make%\%Model% as value for my Windows 7 x64. You have to adapt this to your Out-of-Box tree.

As I use a DriverGroup I’ve disabled the ‘Inject Drivers’ task.

Customsettings.ini

As my Task Sequence handles everything, there isn’t anything needed here.

If you don’t like to use a new Task in your TS, you can add DriverGroup variables in customsettings.ini like this:

DriverGroup_001=%Make%\%Model%

DriverGroup_002=Printers

2. Selection Profiles

New in MDT 2010 are DriverSelectionProfiles. These are easy for new MDT admins, very straight forward and easy to use.

Overview:

First you have to create a Profile (or use one of the default profiles):

You can even select Packages and Applications, use it for “bad drivers” aka driver setup packs.

Select what drivers you want to add to the profile;

After making the profiles you can use them in your Task Sequences. The default ‘Inject Drivers’ settings are on the left, the customized one on the right:

You can add  Selection Profiles for drivers/packages or whatever you want. Just add an extra step in your task sequence like above.

Customsettings.ini

As with DriverGroups you can choose to handle the DriverSelectionProfile in customsettings.ini or in your TS.

Example:

DriverSelectionProfile=Dell Latitude D520 x64

1) Manage your current server certificates.
2) Enable certificates for Exchange 2007 Services (POP, IMAP, SMTP, IIS, UM).
3) Generate an Exchange 2007 Certificate Signing Request and process the Certificate Authority answer.
4) Generate an Exchange 2007 Self-Signed certificate (not for production use).
5) Easily include additional subject names in a single certificate.
6) Import & Export ability for existing certificates.
To read more about Certificate Use in Exchange 2007 at Microsoft TechNet follow the link:

Certificate Manager for Exchange Server 2007 is currently offered by U-BTech Solutions free of charge

Certificate Manager for Exchange Server 2007 Flash Demonstration

Download – Certificate Manager for Exchange 2007

SOURCE

Exchange Server 2010

Product name	Build number
Microsoft Exchange Server 2010 RTM	14.0.639.21
Update Rollup 1 for Exchange Server 2010	14.0.682.1
Update Rollup 2 for Exchange Server 2010	14.0.689.0
Update Rollup 3 for Exchange Server 2010	14.0.694.0
Update Rollup 4 for Exchange Server 2010	14.0.702.1

Exchange Server 2010 SP1 

Product name	Build number
Microsoft Exchange Server 2010 SP1	14.1.218.15

Exchange 2007 RTM

Exchange Server 2007 Service Pack 1

Exchange Server 2007 Service Pack 2

Exchange Server 2007 Service Pack 3

De Onderwerpen:

Exchange
- High Availability in Exchange 2007
- Message Hygiene in Exchange Server 200731
- Using Exchange 2007 for Resource Booking
- Controlling Email Messages using Exchange’s Transport Rules
- Exchange 2007 Mailbox Server Clustering
- Top Tips for Exchange Admins
- Exchange Database Technologies
- Message Classifications in Exchange 2007
- Deploying Exchange 2007 on Windows Server 2008
- Exchange Server Log File Replay
- Configuring Exchange Server 2007 to Support Information Rights Management
- Reporting on Mobile Device Activity Using Exchange 2007 ActiveSync Logs
- Online Exchange Backups
- Optimizing Exchange Server 2007
- Exchange: Recovery Storage Groups
- Exchange E-mail Addresses and the Outlook Address Cache
- Upgrading to Exchange Server 2007
- Goodbye Exchange ExMerge, Hello Export-Mailbox
- Determining MS Exchange Disk Performance
- Upgrading to Exchange Server 2007: Part 2
- Message Tracking in Exchange 2007
- Third Party High Availability and Disaster Recovery Tools for Microsoft Exchange Server
- Exchange Server 2010 – The First Public Beta Version
- Emulating the Exchange 2003 RUS for Out-of-Band Mailbox Provisioning in Exchange 2007
- Using Exchange 2007 Transport Rules to Protect the First Entry in the Address Book
- Cluster Continuous Replication Network Design
- Building an Exchange Server 2007 environment
- An Introduction to Messaging Records Management
- Installing Hyper-V and Beyond
- Restricting Outlook Client Versions in Exchange 2007
- Using Twitter and PowerShell to Find Technical Information and Join a Community
- Update: Exchange Server 2010 Release Candidate
- Exchange backups on Windows Server 2008
- Moving to Office Communications Server 2007 R2
- Monitoring and Scheduling Exchange 2007 Database Online Maintenance
- Exchange 2010 High Availability
- Implementing Cluster Replication – Part 1
- The Active Directory Recycle Bin in Windows Server 2008 R2
- Using Group Policy to Restrict the use of PST Files
- Introduction to Exchange Server 2010
- The Ego and the System Administrator
- Implementing Windows Server 2008 File System Quotas
- Implementing Cluster Continuous Replication, Part 2
- Active Directory Management with PowerShell in Windows Server 2008 R2
- Upgrade Exchange 2003 to Exchange 2010
- Customizing the Outlook Address Book

General Articles
- A SysAdmin’s Guide to Change Management
- A SysAdmin’s Guide to Users
- Change Management – What It Is and Why You Need It
- Manage Stress Before it Kills You
- Hiring System Administrators
- Increase Your Value as a Professional in the Technical Industry
- The Art of Dealing with People

Virtualization
- Virtual Exchange Servers
- Virtualizing Exchange: points for discussion
- Build Your Own Virtualized Test Lab
- A Beginner’s Guide to Virtualizing Exchange Server – Part 1
- A Beginner’s Guide to Virtualizing Exchange Server – Part 2
- Windows Server Virtualisation: Hyper-V, an Introduction
- Increasing the Availability of Virtualized Applications and Services
- Microsoft Hyper-V Networking and Configuration – Part 1

Unified Messaging
- An Introduction to Unified Messaging
- Moving to Office Communications Server 2007 R2

PowerShell
- Managing Exchange 2007 Mailbox Quotas with Windows PowerShell
- So You Thought PowerShell Was Only For Exchange 2007

Downloaden klik op het boek

Optie 1 Exchange Management Shell

Optie 2 Powershell

Get-ReceiveConnector "Default *" | Set-ReceiveConnector

-PermissionGroups:AnonymousUsers,ExchangeUsers,ExchangeServers

Powershell
Move-OfflineAddressBook -Identity ‘\Default Offline Address Book’ -Server ‘Ward-Ex02′

Powershell

Set-TransportConfig –ExternalPostmasterAddress postmaster@wardvissers.nl

Set-TransportConfig -MaxSendSize ‘20mb’

Set-TransportConfig -MaxRecipientEnvelopeLimit 5000

Set-TransportConfig -MaxReceiveSize ‘20mb’

Optie 1 EMC

Optie 2 Powershell

New-SendConnector –Name ‘External’ –Usage ‘Internet’ –AddressSpaces ‘SMTP:*;1’

–DNSRoutingEnabled $true –UseExternalDNSServersEnabled $false –Fqdn ‘mail.wardvissers.nl’

Powershell
New-PublicFolderDatabase "Public Folders" -Server SERVER01

Mount-Database "Public Folders"

New-PublicFolderDatabase Support -Server SERVER02 -EdbFilePath E:\Databases\Support\Support.edb -LogFilePath D:\Logs\Support

Mount-Database Support

RemoteServerAdministrationTools-Roles

RemoteServerAdministrationTools-Roles-CertificateServices
RemoteServerAdministrationTools-Roles-CertificateServices-CA
RemoteServerAdministrationTools-Roles-CertificateServices-OnlineResponder
RemoteServerAdministrationTools-Roles-AD
RemoteServerAdministrationTools-Roles-AD-DS
RemoteServerAdministrationTools-Roles-AD-DS-SnapIns
RemoteServerAdministrationTools-Roles-AD-DS-AdministrativeCenter
RemoteServerAdministrationTools-Roles-AD-DS-NIS
RemoteServerAdministrationTools-Roles-AD-LDS
RemoteServerAdministrationTools-Roles-AD-Powershell
RemoteServerAdministrationTools-Roles-DHCP
RemoteServerAdministrationTools-Roles-DNS
RemoteServerAdministrationTools-Roles-FileServices
RemoteServerAdministrationTools-Roles-FileServices-Dfs
RemoteServerAdministrationTools-Roles-FileServices-Fsrm
RemoteServerAdministrationTools-Roles-FileServices-StorageMgmt
RemoteServerAdministrationTools-Roles-HyperV
RemoteServerAdministrationTools-Roles-RDS
RemoteServerAdministrationTools-Features

RemoteServerAdministrationTools-Features-BitLocker
RemoteServerAdministrationTools-Features-Clustering
RemoteServerAdministrationTools-Features-GP
RemoteServerAdministrationTools-Features-LoadBalancing
RemoteServerAdministrationTools-Features-SmtpServer
RemoteServerAdministrationTools-Features-StorageExplorer
RemoteServerAdministrationTools-Features-StorageManager
RemoteServerAdministrationTools-Features-Wsrm

Step 1. Installatie the RSAT MSU pakket

wusa  x86fre_GRMRSAT_MSU.msu /quiet  (x86)
wusa  amd64fre_GRMRSATX_MSU.msu /quiet  (x64)

Stap 2 Alle beschikbare opties:

dism /Online /Get-Features

Stap 3: Aanzetten van de beschikbare Opties

dism /Online /Enable-Feature /FeatureName:<FeatureName>

Voorbeeld
Ik wil Active Directory snap ins uitrollen.

wusa Windows6.1-KB958830-x86.msu /quiet
dism /online /enable-feature /featurename:RemoteServerAdministrationTools
dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles
dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD
dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD-DS
dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD-DS-SnapIns

Wat is nu de EcoShell:
De Virtualization EcoShell biedt een eenvoudige, consistente en geïntegreerde beheer user interface voor het creëren, debuggen en vereenvoudiging van het beheer van Windows PowerShell scripts.
Voor downloads en informatie over het installeren van de Virtualisatie EcoShell, bezoekt u de Virtualisatie EcoShell download pagina.

Meer en meer bedrijven gebruiken Windows PowerShell scripts op verschillende platformen.
De Virtualisatie EcoShell gepositioneerd is voor IT-beheerders, adviseurs, en consultants die alles moeten beheren en terug kerende taken te automatiseren . Gecentraliseerd beheer van servers. De Virtualisatie EcoShell bespaart dagelijks tijd voor beheerders voor het beheer van virtuele omgevingen.

Wat heb je nodig om er gebruik van te kunnen maken.

Windows PowerShell Version 1.0
VMware PowerCLI 4.0
Quest PowerShell Commands for Active Directory Version 1.2
32-Bit  |  64-Bit
Virtualization EcoShell Build 1.2.0.154

Zo ziet de Virtualization EcoShell er uit.

2. Open het menu Start, ga naar Alle programma’s dan Accessoires dan Windows PowerShell. Open een verhoogde Windows PowerShell console en voer het volgende commando:

Import-Module ServerManager

3. Gebruik de Servermananger cmdlet het installeren van de nodige onderdelen van het besturingssysteem:

servermanagercmd -i NET-Framework
servermanagercmd -i RSAT-ADDS
servermanagercmd -i Web-Server
servermanagercmd -i Web-Basic-Auth,
servermanagercmd -i Web-Windows-Auth
servermanagercmd -i Web-Metabase
servermanagercmd -i Web-Net-Ext
servermanagercmd -i Web-Lgcy-Mgmt-Console,
servermanagercmd -i WAS-Process-Model,
servermanagercmd -i RSAT-Web-Server
servermanagercmd -i Web-ISAPI-Ext
servermanagercmd -i Web-Digest-Auth
servermanagercmd -i Web-Dyn-Compression
servermanagercmd -i NET-HTTP-Activation
servermanagercmd -i RPC-Over-HTTP-Proxy
servermanagercmd -Restart

http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx

4. Nadat het systeem opnieuw is opgestart, meldt u aan als beheerder, opent u een verhoogde Windows PowerShell console en configureren van de Net.Tcp Port Sharing Service voor Automatisch opstarten door het volgende commando:

Set-Service NetTcpPortSharing -StartupType Automatic

5. Installeer Exchange 2010
 

Als je alle powershell commando’s in een document zet dan heb je alle e-mail adressen.

Public Folder
Get-Mailpublicfolder | format-list Name, Emailaddresses > c:\publicfolder.txt

Mailbox
Get-Mailbox | format-list Name, Emailaddresses > c:\mailbox.txt

Distributiongroup
get-distributiongroup  | format-list Name, Emailaddresses > c:\distributiongroup.txt

MailContact
get-mailcontact  | format-list Name, Emailaddresses > c:\mailcontact.txt

 Michael Niehaus heeft een overzicht gemaakt van alle nieuwe functies en stuk voor stuk uitlegt wat het doet. Ik heb even een mooi overzicht van gemaakt:

Automatically update MDT 2010 boot images in WDS
Automating Long-Running MDT 2010 Tasks

MDT 2010 New Feature #1: Logging directly to the network
MDT 2010 New Feature #2: Gathering virtualization details
MDT 2010 New Feature #3: Suspend and resume a Lite Touch task sequence
MDT 2010 New Feature #4: Folders everywhere
MDT 2010 New Feature #5: Support for multiple deployment shares
MDT 2010 New Feature #6: Drag and drop
MDT 2010 New Feature #7: Boot image creation optimized
MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE
MDT 2010 New Feature #9: Copy and paste support in the Deployment Workbench task sequence editor
MDT 2010 New Feature #10: Detection of signed drivers
MDT 2010 New Feature #11: Windows 7 and Windows Server 2008 R2 support
MDT 2010 New Feature #12: USMT 4.0 hardlink support
MDT 2010 New Feature #13: New task sequence templates
MDT 2010 New Feature #14: Database improvements
MDT 2010 New Feature #15: Finish actions
MDT 2010 New Feature #16: PowerShell support
MDT 2010 New Feature #17: Customizable boot image process
MDT 2010 New Feature #18: Selection Profiles
MDT 2010 New Feature #19: Improved Driver Management
MDT 2010 New Feature #20: General Purpose ConfigMgr wizard
MDT 2010 New Feature #21: Copying extra folders

2. Maak onder Out-of-Box Drivers twee mapjes aan. Zie de afbeelding hieronder.
 

3. Importeer de drivers uit de 7zip bestand.

4. Klik de MDT Deployment Share weer aan en klik op Update Deployment Point

5. 

6. Wil je dit met Powershell doen klik op view script dan krijg het volgende powerscript te zien:

Add-PSSnapIn Microsoft.BDD.PSSnapIn
New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\Distribution"
update-MDTDeploymentShare -path "DS001:" -Verbose

7. Vergeet niet om de oude LiteTouchPE_x64 & LiteTouchPE_x86 in WDS te verwijderen en opnieuw toe te voegen.

2. Installeer op een Windows 2008 machine Powershell als Feature

3. Installeer de nieuwe WAIK Versie die ook Windows 7 & Windows 2008 R2 ondersteund.

4. Installeer MDT 2010

5. Start Deployment Workbench op.

Kies voor Open Deployment Share
 
 
Geef het oude path in de van de oude distributie map. Vergeet ook het vinkje niet aan te zetten.
 
 

5. Open Windows Deployment Services.

6. Gooi de oude Boot Images weg.

7. Voeg de twee nieuwe die tijdens de upgrade gemaakt zijn toe
LiteTouchPE_x86.wim
LiteTouchPE_x64.wim

Klik HIER om het boek online te bekijken.

Heb er maar even een mooie verzameling van gemaakt.

Zoals normaal je heb je geen “tijd” om alles te lezen of je moet geen leven hebben

Als je iets zit wat je leukt wat er bij zit vindt doe je voordeel er mee.

Windows Server 2008 R2: Remote Desktop Services – The Series (P1)
Windows Server 2008 R2: Remote Desktop Services – The Series (P2)
Windows Server 2008 R2- Remote Desktop Services – The Series (P3)
Windows Server 2008 R2- Remote Desktop Services – The Series (P4)
Windows Server 2008 R2- Remote Desktop Services – The Series (P5)

Part 1 Master Your Environment with System Center Configuration Manager 2007
Part 2 Master Your Environment with System Center Configuration Manager 2007
Part 3 Master Your Environment with System Center Configuration Manager 2007
Part 4 Master Your Environment with System Center Configuration Manager 2007

Hyper-V R2- Failover & Live Migration
Hyper-V R2- Making Highly Available VMs
Hyper-V R2- Making Highly Available VMs
Hyper-V R2- Dynamic Storage
Hyper-V R2- USB over Network with Fabulatech
Hyper-V R2- Introducing Cluster Shared Volumes
Hyper-V R2- Building a Hyper-V R2 Cluster
Hyper-V R2- Initial Installation & Configuration

Demo 1 – Hyper-V Live Migration
Demo 2 – Boot From VHD
Demo 3 – Windows PowerShell 2.0 Remoting
Demo 4 – Active Directory Enhancements

Microsoft Deployment Toolkit – building install media for Windows 7
Windows XP Migration to Windows 7 RC using MDT Beta 1 – Part 1- The OS Install
Windows XP Migration to Windows 7 RC using MDT 2010 Beta 1 – Part 2- How To Build It…

Open Source Software (OSS) on Windows Server 2008

Exchange 2010 Demo: Read and Reply State
Exchange 2010 Demo: Conversation View
Exchange 2010 Demo: Move Conversation
Exchange 2010 Demo: Nickname Cache
Exchange 2010 Demo: UM Card

Interview with Kristian Andaker on Transitions to Exchange Server 2010
Interview with Kristian Andaker on Exchange 2010 OWA
Interview with Matt Gossage on Exchange Server 2010 and Storage
Interview with Scott Schnoll on Exchange 2010 High Availability
Interview with Scott Schnoll on Backup Strategy in Exchange 2010
Interview with Becky Benfield on Exchange 2010 Site Resiliency at Tech Ed 2009

Waarom zijn dagen zo kort!!!!!!!!!!!!!