MDT 2010 Automatically Move Computers to the Right OU

When I deploy client computers you have always 2 client Tasks. One for Laptops and one for Desktops.
I already blogd about joing domain. Jou can find it here. http://www.wardvissers.nl/2009/12/20/mdt-2010-join-domain/.

I had a issue joining the computers to the right ou for the two tasks.

I found a great solution to fix it.

Here is how I did it.

Open the right Task Sequence. I my case it was laptop.

This is de default setting
image

Change this to: Gather local data and proces rules. Fill at Rules files customsettings.ini in.
image

Open Customsettings.ini

Change the following

[Settings]
Priority=Default
Properties=MyCustomProperty

to

[Settings]
Priority=TaskSequenceID, Default
Properties=MyCustomProperty

Add the following text.

[LAPTOP]
MachineObjectOU=ou=laptops,ou=ward,dc=wardvissers,dc=local

You can do this also for Desktops.

When you deploy a new computer the computer is now in the right OU.  I love MDT Open-mouthed smile

FREE Exchange 2010 Training available

Exchange 2010 Upgrade and Deployment (HOLO)

This 300 level hands-on labs online course (including seven hands-on labs) will prepare learners with the knowledge to engage with customers to help them implement best practices for smooth Exchange 2010 upgrades and deployments. These hands-on labs online (HOLOs) are provided at no charge to Microsoft partners, and provide IT Professionals with the essential information they need to setup, deploy, and configure Microsoft Exchange Server 2010.  The course will address gaps in knowledge around topics such as new features, upgrade paths, tools and processes to support upgrade and deployment planning.

Training includes the following curriculum:

Course (Online): Using Exchange 2010 Tools to Plan a Deployment (Part 1)

Course (Online): Using Exchange Tools to Plan a Deployment (Part 2)

Course (Online): Exchange 2010 Setup, Deployment, and Server Role Configuration

Course (Online): Configuring Mail Flow and Outlook Web Access

Course (Online): Moving Mailboxes to Exchange 2010

Course (Online): Moving Other Services to Exchange 2010 (Part 1)

Course (Online): Moving Other Services to Exchange 2010 (Part 2)
exchange 2010

Thanks to

Bryan Von Axelson

Home folders renamed to My Documents

When you redirect users home folders to network share the folders are show as My Documents folder.

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 Sad smile

Richard Willis created a nice powershell script that will do it for you Open-mouthed smile
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
}
}

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

Beta Outlook 2007 Online Archive Support

I read on Henrik Walther blog about the Outlook 2007 Online Archive Support. So I checked this on my home lab. You just need to apply the Office Outlook 2007 hotfix package (released back in October 2010) and voilá, you now have access to your online archive from Outlook 2007 Open-mouthed smile. Can’t wait when it is fully supported.
.
image

After installing Rollup 1 for Exchange 2007 SP3 IMAP is now serving most text/plain parts as text/html

After installing Rollup 1 for Exchange 2007 SP3 IMAP is now serving most text/plain parts as text/html instead. I had some issue with a simple mail import tool that now imported all mail with html codes.

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

MAPI or an unspecified service provider. ID no: 00000000-0000-00000000

When you want to import a mailbox you get some times the following error:

MAPI or an unspecified service provider. ID no: 00000000-0000-00000000
image

Solution is very easy: Give yoursell full access rights to a mailbox Smile

Add-MailboxPermission -identity "user" -Accessrights FULLACCESS -User "yourusername"

Migrating to Exchange 2010 & PDA Sync Issues

Some day’s ago I was testing some PDA’s Windows Mobile and Nokia’s for a Exchange Migration to Exchange 2010.

I created a little procure to test it.

1. PDA sync at first with ISA 2006 against Exchange 2007.

2. Shutdown the ISA 2006 Server

3. Starting the TMG Server

4. Checking if the PDA would sync. (The PDA should be sync with legacy.wardvissers.nl automatically )

5. Move the Mailbox to Exchange 2010 and check again if the PDA sync works.

 

Windows Mobile PDA (6.1).

1. Works fine

2.

3.

4. The PDA will be redirected to legacy.wardvissers.nl and pda sync works great. The User had nothing to do.

5. Moving the Mailbox to Exchange 2010 there is no problem. The user will automatically redirected from legacy.wardvissers.nl to webmail.wardvissers.nl with out any problems.

Nokia E71/E72 (Mail for Exchange Client 3.0.73)

1. Works fine

2.

3.

4. PDA don’t sync anymore. The user must change the sync url manual to legacy.wardvissers.nl than it works again.

5. Moving the Mailbox to Exchange 2010 there is no problem. If you change the url to legacy.wardvissers.nl you must change it manually back.

Nokia E71/E72 With (Road Sync 4.0/5.0)

1. Works fine

2.

3.

4. PDA don’t sync anymore. The user must change the sync url manual to legacy.wardvissers.nl than it works again.

5. Moving the Mailbox to Exchange 2010 there is no problem. If you change the url to legacy.wardvissers.nl you must change it manually back.

Conclusion

Moving PDA users to Exchange 2010 can be a pain in the ass. Best practice is create a list of all PDA users and move them first to Exchange 2010 and than all other users.

Exchange 2010 PST Import

Mailbox Import Role

When you want to import some pst’s you need some rights from doing this. This is a one time setting.

New-ManagementRoleAssignment ?Role ?Mailbox Import Export? ?User Administrator

Name                           Role              RoleAssigneeName  RoleAssigneeType  AssignmentMethod  EffectiveUserName

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

Mailbox Import Export-Admin… Mailbox Import… Administrator     User              Direc

Set Mailbox Language

Set-MailboxRegionalConfiguration -Identity ward -Language nl-nl -DateFormat "dd-mm-yyyy

If you want this for multiple mailboxes you case the following script

$a=get-Mailbox *
$a | Set-MailboxRegionalConfiguration -language nl-nl -DateFormat "dd-mm-yyyy

Import a mailbox

New-MailboxImportRequest -Mailbox ward -FilePath \\win701\c$\ward.pst

Remove  newmailimportRequest

Get-MailboxImportRequest -Status Completed | Remove-MailboxImportRequest

Status

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics | ft TargetAlias,Percent*,BytesTransferred*

Multiple Mailboxes at the same time

Dir \\win701\c$\Exmerge-PSTS\*.pst | %{

    New-MailboxImportRequest ?Name ImportOfPst ?BatchName ImportPstFiles `

        ?Mailbox $_.BaseName ?FilePath $_.FullName

}

Exchange 2010 & Outlook 2010 Automatically Shared Mailboxes

When you set full access permissions with the Exchange 2010 management console on a mailbox,the user which has be giving full access right now there will filed a new property.
image

The property is MSExchDelegateListLink. You can check it with adsiedit.
image

When you open now Outlook 2010 you can now see that Wardtest is automatilly Added

image

And additional mailboxes is empty
image

When you migrating from Exchange 2007 to Exchange 2010 and upgraded the Clients to Outlook 2010
Use dis script to set the MSExchDelegateListLink object automatically. Test I first. It’s your own risk.

$a=get-MailboxPermission * | where {$_.IsInherited –eq $False –and $_.accessrights –eq “FullAccess”}
$a | remove-MailboxPermission –confirm:$false
$a | add-MailboxPermission

Save the scripts to MSExchDelegateListLink.ps1

It works great Open-mouthed smile
Source

Translate »