The View desktops we’ve got setup are using linked clones and persistent disks which map to the D:\ in the users sessions. Of course this means the users profile is loaded to the D:\ instead of C:\ in the virtual desktops. My issue is, when a new users comes from our old environment into the test view setup, their Outlook is trying to find their OST file on the C:\ (c:\document and settings\…etc). The users data has been loaded to the D:\ though. The only way I’ve found to get around this is going into the Contol Panel in the users session, deleting their Outlook profile,

Solution:

Microsoft saves information about profile under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook

So, within regedit, I right-clicked on HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook then chose Export. For Save as Type, I changed the value to "Text Files (*.txt)". I then opened the text file I created with Notepad. You can’t just search for "Outlook.ost", since there are null, i.e. 00, characters stored between each character. They show up in an ASCII representation as dots. E.g. Outlook.ost would be O.u.t.l.o.o.k…o.s.t.

Since the "Outlook.ost" could be broken across multiple lines, I decided just to search for o.s.t. I found the following in the text file I had created.

Value 31

  Name:            001f6610

  Type:            REG_BINARY

  Data:           

00000000   43 00 3a 00 5c 00 44 00 – 6f 00 63 00 75 00 6d 00  C.:.\.D.o.c.u.m.

00000010   65 00 6e 00 74 00 73 00 – 20 00 61 00 6e 00 64 00  e.n.t.s. .a.n.d.

00000020   20 00 53 00 65 00 74 00 – 74 00 69 00 6e 00 67 00   .S.e.t.t.i.n.g.

00000030   73 00 5c 00 4a 00 69 00 – 6d 00 5c 00 4c 00 6f 00  s.\.J.i.m.\.L.o.

00000040   63 00 61 00 6c 00 20 00 – 53 00 65 00 74 00 74 00  c.a.l. .S.e.t.t.

00000050   69 00 6e 00 67 00 73 00 – 5c 00 41 00 70 00 70 00  i.n.g.s.\.A.p.p.

00000060   6c 00 69 00 63 00 61 00 – 74 00 69 00 6f 00 6e 00  l.i.c.a.t.i.o.n.

00000070   20 00 44 00 61 00 74 00 – 61 00 5c 00 4d 00 69 00   .D.a.t.a.\.M.i.

00000080   63 00 72 00 6f 00 73 00 – 6f 00 66 00 74 00 5c 00  c.r.o.s.o.f.t.\.

00000090   4f 00 75 00 74 00 6c 00 – 6f 00 6f 00 6b 00 5c 00  O.u.t.l.o.o.k.\.

000000a0   6f 00 75 00 74 00 6c 00 – 6f 00 6f 00 6b 00 2e 00  o.u.t.l.o.o.k…

000000b0   6f 00 73 00 74 00 00 00 -                          o.s.t…

I could also have searched in the .reg file I created when I exported the registry information from the other computer. But, again, you can’t just search for "Outlook.ost" in the .reg file you created, either, since the information in it is the hexadecimal representation of the binary data in the registry keys. You would need to convert a string, such as "ost" to hexadecimal form. You can do that at String – ASCII, HEX, Binary Converter. In the String field, I put in ost. The converter showed me the equivalent hex value is 6F 73 74. Note: the converter shows decimal/ASCII, binary, and hex values. Make sure you use the correct one. Also note that the hexadecimal representation of "OST" is not the same as "ost". Since the error message I received referred to Outlook.ost, I converted "ost" to hexadecimal. Again, it may be better to limit the length of the string to reduce the chance it will be broken across multiple lines in the file.

Once you have the hexadecimal equivalent of the ASCII string, you still can’t just search for it, i.e. a search for 6F7374 wouldn’t work. The hexadecimal numbers are stored in the .reg file with commas and the null character, 00, between them. I.e., I would need to search for 6f,00,73,00,74 instead.

In the .reg file found it among the following lines:

"001f6610"=hex:43,00,3a,00,5c,00,44,00,6f,00,63,00,75,00,6d,00,65,00,6e,00,74,\

  00,73,00,20,00,61,00,6e,00,64,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,\

  67,00,73,00,5c,00,4a,00,69,00,6d,00,5c,00,4c,00,6f,00,63,00,61,00,6c,00,20,\

  00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,00,5c,00,41,00,70,00,70,00,\

  6c,00,69,00,63,00,61,00,74,00,69,00,6f,00,6e,00,20,00,44,00,61,00,74,00,61,\

  00,5c,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,5c,00,4f,00,\

  75,00,74,00,6c,00,6f,00,6f,00,6b,00,5c,00,6f,00,75,00,74,00,6c,00,6f,00,6f,\

  00,6b,00,2e,00,6f,00,73,00,74,00,00,00

I noticed it was associated with a "001f6610" entry. When I had searched the text file, I had also seen Outlook.ost associated with "Name: 001f6610".

You can delete the following registry key with group policy preferences to disable using Offline Folders after disabling Use Cached Mode in Group Policy:

HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook\13dbb0c8aa05101a9bb000aa002fc45a\001f6610

1. Using Powershell

A minor schema change

First stop, the AD Schema. A minor schema modification is required to flip the thumbnailPhoto attribute to make it replicate to the Global Catalog.

1. If you haven’t registered the Schema MMC snap-in on the server you want to make this change on, go ahead and do so using the following command:

   Regsvr32 schmmgmt.dll

2. Fire up a MMC console (Start -> Run -> MMC) and add the Schema snap-in

3. In the Active Directory Schema snap-in, expand the Attributes node, and then locate the thumbnailPhoto attribute. (The Schema snap-in lists attributes by its ldapDisplayName).

4. In the Properties page, select Replicate this attribute to the Global Catalog, and click OK.

   

   Figure 1: Modifying the thumbnailPhoto attribute to replicate it to Global Catalog

Loading pictures into Active Directory

Now you can start uploading pictures to Active Directory using the Import-RecipientDataProperty cmdlet, as shown in this example:

Import-RecipientDataProperty -Identity "Ward VIssers" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\wardvissers.jpg" -Encoding Byte -ReadCount 0))

To perform a bulk operation you can use the Get-Mailbox cmdlet with your choice of filter (or use the Get-DistributionGroupMember cmdlet if you want to do this for members of a distribution group), and pipe the mailboxes to a foreach loop. You can also retrieve the user name and path to the thumbnail picture from a CSV/TXT file.

2. Using a Free tool like Outlook Photos from Exclaimer

Download the Tool HERE

The tool is easy to use .

Prerequisites

User Preferences

Domain user – The logged in user’ account is required to be an Active Directory account.

Domain computer – The computer the user is logged into needs to be joined to an Active
Directory domain.

Active Directory permissions – The logged in user must have permission to upload photos to the required Active Directory accounts. (Alternate credentials can be supplied or control of the thumbnailPhoto field can be delegated to the logged in user.)

Operating System

• Windows Server 2003 x86 (including all service pack levels).
• Windows Server 2003 R2 x86 and x64 (including all service pack levels).
• Windows Server 2008 x86 and x64 (including all service pack levels).
• Windows Server 2008 R2 x86 and x64 (including all service pack levels).
• Windows Small Business Server 2003 (including all service pack levels).
• Windows Small Business Server 2008.
• Windows Small Business Server 2011.
• Windows XP x86 and x64 (including all service pack levels).
• Windows Vista x86 and x64 (including all service pack levels).
• Windows 7 x86 and x64 (including all service pack levels).

Other Software

Microsoft Outlook 2010 x86 and x64

Microsoft .NET Framework 3.5 SP1

Microsoft Exchange 2010 RTM and above

Active Directory

You must be logged into an Active Directory domain to run the application.

Active Directory Forest
Domain and Forest functional level of Windows Server 2008 and above.
For Domain or Forest functional level of Windows Server 2003, the Windows Server 2008 Forest preparation must first be complete.

Screenshots

   

Solution Uninstalling KB2412171

%windir%\System32\msiexec.exe /package <Office 2007 product code> /uninstall <patch code for the MSP from KB2412171> /Q /L*V %temp%\Remove_KB2412171.log Product codes (or “GUIDs”) for Office 2007 and Outlook 2007 are as follows: Standard: {90120000-0012-0000-0000-0000000FF1CE} Professional: {90120000-0014-0000-0000-0000000FF1CE} Professional Plus:{90120000-0011-0000-0000-0000000FF1CE} Enterprise:{90120000-0030-0000-0000-0000000FF1CE} Outlook 2007 Standalone: {90120000-001A-0000-0000-0000000FF1CE} Patch codes for the MSP files related to KB2412171 are as follows: {7961E819-93A5-40A8-8469-4BE2FBBFACEF}  (for the original patch) {752A0B7C-BD24-4362-AC86-AB63FEE6F46F} (for the re-release patch)

For my did this the trick
%windir%\System32\msiexec.exe /package {90120000-0030-0000-0000-0000000FF1CE} /uninstall {752A0B7C-BD24-4362-AC86-AB63FEE6F46F} /Q /L*V c:\Remove_KB2412171.log

Needed.
- Office 2010 ISO
- Office 2010 Administrative Template files (ADM, ADMX/ADML) and Office Customization Tool

1. Make sure you have a working Office 2007 deployment. Check this How to deploy Office 2007 with MDT

2. Extract the Office 2010 ISO to the application folder on de MDT Server

2. Extract AdminTemplates_32.exe or AdminTemplates_64.exe to a folder.

3. Copy the Admin folder that you can find in the extracted folder to the Office 2010 folder that you created at step 1.

4. Run setup.exe /admin

5. Check the Screenshots for the settings

6. Save the file in Updates folder that you find in Office folder. I named the file setup.MSP

7. Create a new application without source files.

Command Line is:
setup.exe /adminfile “\\mdtservername\deploymentshare$\Applications\Microsoft Office 2010 x86\Updates\setup.msp”

A few customers, partners, and individual folks in the Exchange community have reported that a few of the Exchange 2010 users running Outlook 2003 randomly have issues connecting to their mailbox. After examining the mail profile in Outlook 2003, you can see the Exchange server name appears as Instance-<GUID> where <GUID> is a randomly generated GUID (or number). Re-resolving (‘Check Name’) the appropriate server name in the Outlook mail profile resolves the issue.

Figure 11: Instance-GUID issue in Outlook 2003

Note
Seeing Instance-<GUID> in conversation between an Outlook 2003 client and an Exchange 2010 server is normal (when Instance-<GUID> appears inside Outlook in the folders list view on left hand side); It does NOT mean you are hitting this particular issue. You experience this issue if the Outlook mail profile gets updated to refer to the Exchange server as Instance-GUID.

The problem behavior can be triggered by networking issues, patch applications, server reboots, etc. It requires Outlook 2003 to lose connectivity to Exchange and have a delegate mailbox logon attempted on a connection before the primary mailbox logon is attempted on that connection. This can affect users who are accessing shared mailboxes or folders of other users from their Outlook 2003 while connecting to Exchange 2010.

Currently there is no proper resolution available for this issue. However, to remediate this issue temporarily, simply re-resolve the Exchange server name in the Outlook mail profile. If possible, you may also remove the shared mailboxes or shared folders (like calendars) from the profile, preventing this issue from occurring in the future or create a new mail profile in Outlook.

Microsoft is working to investigate this issue for a fix. You can contact Microsoft Support to report this issue and request further assistance. Currently no KB article exists for this issue.

Update:

Microsoft has confirmed this to be a bug and the bug was assigned to the Outlook team within Microsoft. It has been fixed and a hotfix can be downloaded here: http://support.microsoft.com/kb/2510153

Special Thanks to Henrik Walther & Jaap Wesselius

Step 1: Download the Office 2010 English version booth will be in x86 & x64

Step 2. Download the Office 2010 (language) Multilanguage iso only available from the Microsoft Volume Licensing site. Both in x86 en x64.

Step 3. Add the Office 2010 English version to MDT 2010 here office-2010-uitrollen-met-mdt-2010

Step 4. Extract the Office 2010 (language) Multilanguage iso with 7zip in the same application folder witch you created in Step 3.

Step 5. When you open MDT 2010 management console and you go to the Office 2010 Application that you added in step 3. You wil see that MDT sees more the one language. In my case it was en-us and nl-nl. The Screenshot is from the older MDT 2010 you MDT sees Office 2010 as Office 2007. MDT 2010 beta 1 supports Office 2010. I found till now no issues deploying Office 2010.

Step 6. Check the languages that you want. Check the Screenshot how i did it.

Step 7. Deploy the a Windows XP or Windows 7 client with Office 2010 Multilanguage versions.

Step 8. You can check with Microsoft Office 2010 Language Preferences or the languages that you configured are installed.

Step 9. Use Group Policy to set the language settings for users

1. Download the Office 2010 policy template files to your computer. You will find them HERE

2. Make a new GPO named Office 2010 languages settings it is a user policy.

3. Under User Configuration in the console tree, right-click Administrative Templates.

4. Click Add/Remove Templates, and then click Add.

5. In the Policy Templates dialog box, click the template that you want to add, and then click Open.

6. After you add the Office 2010 templates, click Close.

7. Open the Group Policy object (GPO) for which you want to set policy.

8. Double-click User Configuration and expand the tree under Administrative Templates.

9. Locate language-related policies in the Microsoft Office 2010 \ Language Settings node.

10. Select the languages that you want to use for each setting.

11. Save the GPO.

12. Go Testing

Office is not activated

Determining Which Activation Method Office is Using – KMS or MAK

Click the start menu and enter cmd /k cscript “%programfiles%\Microsoft Office\Office14\ospp.vbs” /dstatus in the search box.

If running 32 bit Office 2010 on 64 bit Windows, %programfiles% above should be replaced with %programfiles(x86)%.

Not Activated

Checking if a DNS Domain is Configured for KMS Auto-Discovery

To check if a DNS domain is configured for KMS auto-discovery, check that a SRV record exists.

nslookup -type=srv _vlmcs._tcp.wardvissers.nl

If a SRV record exists for the domain, the DNS server will detail the SRV record.

C:\>nslookup -type=srv _vlmcs._tcp

Server:  ward-dc02.wardvissers.local

Address:  192.168.150.6

Non-authoritative answer:

_vlmcs._tcp.wardvissers.local SRV service location:

          priority       = 0

          weight         = 0

          port           = 1688

          svr hostname   = ward-dc2.wardvissers.local

If no SRV record exists for the domain, the DNS server will return an error

Verifying that a Windows Computer can Communicate with the KMS Activation Server

KMS activation requires that the machine to be activated has TCP port 1688 open for outbound communication to the activation server.

Verifying that outbound TCP port 1688 is open to the KMS server

1. Download and install the utility portqry.exe from Microsoft. It is a command line utility from Microsoft that reports the port status of a remote host.
2. From a command prompt, run the command:

portqry.exe -n ward-dc02.wardvissers.local -p tcp -e 1688

The command will return “TCP port 1688 (unknown service): LISTENING” if the computer is able to communicate with the KMS server.

If the command returns “TCP port 1688 (unknown service): FILTERED” then the computer is unable to communicate with the KMS server

Manually Specifying the KMS Activation Server

1. Type cmd in the search bar to locate the command window..
2. At the command prompt, type cd\Program Files\Microsoft Office\Office14.

If running 32 bit Office 2010 on 64 bit Windows, Program Files above should be replaced with Program Files (x86).
Run the command cscript ospp.vbs /sethst:ward-dc02.wardvissers.local to manually specify the KMS activation server.

Run the command cscript ospp.vbs /act to activate Office with the KMS server.

Launch Microsoft Outlook 2010 agein
Click to the File tab. Click Help.

Office is activated

X:\Setup.exe /a MSINODISABLEMEDIA=1

msiexec /p C:\SP2\MAINSP3ff.msp /a C:\Office2003\PRO11.msi SHORTFILENAMES=TRUE /qb

In dit schema heeft Microsoft aangegeven welke uitrol methode in welke situatie gebruikt kan worden.

Welke Limieten aan elke uitrol zitten en welke aanbevelingen Microsoft hier over heeft.

Tevens worden aangegeven welke Tools je nodig hebt voor elke uitrol.

Er zijn 3 smaken PDF & VSD & XPS. Downloaden doe je HIER

Aanroep:
C:scripts>cscript exportContacts.vbs /p:C:scriptsoutlookContacts
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

Ward.vcf
Mark.vcf

Script:
==========================================================
‘==     VB Script to Export Outlook Contacts to vCard (vcf) files
‘==
‘==           Copyright © 2008, Dave Moats
‘==
‘== This sample is provided ‘AS-IS’, without any
‘== express or implied warranty. In no event will the
‘== authors be held liable for any damages arising from
‘== the use of this sample code.
‘==
‘== Permission is granted to anyone to use this sample
‘== code for any purpose, including commercial applications,
‘== subject to the following restrictions:
‘==
‘== The origin of this code must not be misrepresented;
‘== you must not claim that you wrote the original code.
‘==
‘== If you use this code, an acknowledgment in the
‘== documentation is requested – shown below:
‘==
‘==             Portions Copyright © 2008,
‘==        Dave Moats (http://www.davemoats.com/).
‘==
‘==========================================================

‘==========================================================
‘== NOTE: watch for wrapped lines and html special
‘==        characters in the web representation of this
‘==        sample code
‘==========================================================

‘==========================================================
‘==
‘== exportContacts.vbs – a script used to export contacts
‘==                        from outlook and save them in
‘==                        vcf format
‘==========================================================
option explicit

‘==========================================================
‘== declare the local variables to be used
‘==========================================================
dim scriptName, namedArgs, folderPath

‘==========================================================
‘== get the name of the running script
‘==========================================================
scriptName = wscript.scriptname

‘==========================================================
‘== get the named command line arguments
‘==========================================================
set namedArgs = wscript.arguments.named

if not namedArgs.exists("p") then
   wscript.echo "Usage: " & scriptName & " /p:<output folder path> is required"
   wscript.echo "Example: cscript " & scriptName & " /p:c:path to the folder"
   wscript.quit
else
   folderPath = namedArgs.item("p")
end if

set namedArgs = nothing

‘==========================================================
‘== now call the subroutine that does all the work
‘==========================================================
exportToVCF folderPath, ".vcf"

wscript.quit

‘==========================================================
‘== sub exportToVCF – subroutine that connects to outlook
‘==                   and exports all contacts to the path
‘==                   specified in the exportPath argument
‘==========================================================
sub exportToVCF(exportPath, ext)
    ‘======================================================
    ‘== declare the local variables
    ‘======================================================
    dim outApp, fldContacts, contactEntry, exp

    ‘======================================================
    ‘== create the outlook object and then get the contacts
    ‘======================================================
    set outApp = createobject("Outlook.Application")
    set fldContacts = outApp.getnamespace("MAPI").getdefaultfolder(10)

    ‘======================================================
    ‘== here we are looping the entries in the contacts
    ‘== folder looking for contacts – when a contact is
    ‘== found it will be exported
    ‘======================================================
    for each contactEntry in fldContacts.items
       if typename(contactEntry) = "ContactItem" then

          dim tmpString, tmpArr, periodLocation, outPath

          tmpString = contactEntry.lastnameandfirstname
          ‘================================================
          ‘== creating the name of the vcf file based on
          ‘== the first and last name fields of the contact
          ‘================================================
          tmpString = replace( tmpString, "’", "" )

          tmpArr = split( tmpString, "," )

          if ubound( tmpArr ) <> 1 then
             wscript.echo tmpString & ext
             outPath = exportPath & "" & tmpString & ext
          else
             if tmpArr(0) = "com" then
                wscript.echo trim(tmpArr(1)) & trim(tmpArr(0)) & ext
                outPath = exportPath & "" & trim(tmpArr(1)) & trim(tmpArr(0)) & ext
             else
                wscript.echo trim(tmpArr(1)) & " " & trim(tmpArr(0)) & ext
                outPath = exportPath & "" & trim(tmpArr(1)) & " " & trim(tmpArr(0)) & ext
             end if
          end if
          contactEntry.saveas outPath, 6

       end if
    next
    ‘======================================================
    ‘== dumping the object references that were created
    ‘======================================================
    set fldContacts = nothing
    set outApp = nothing

end sub

2. Klik op Meer instellingen en klik vervolgens op het tabblad Verbinding.

3. Schakel onder Outlook Anywhere het selectievakje Via HTTP verbinding maken met Microsoft Exchange in.

Opmerking: Als de sectie Outlook Anywhere niet beschikbaar is, is Windows XP Service Pack 2 of hoger vermoedelijk niet op de computer geïnstalleerd.

4. Als u een proxyserver wilt opgeven, klikt u op Proxy-instellingen van Exchange.

1 Voer bij url in je domein naam in waarmee je vanaf buiten kunt connecten naar de exchange server.

2.  Als je een SSL verbinding wilt gebruiken vinkje aan Alleen verbinden via SSL in.

5. Klik onder Instellingen voor proxyverificatie op Basisverificatie of NTLM-verificatie, NTLM-Verificatie wordt standaard gebruikt die uitleg hieronder.

Opmerking: Bij het gebruik van Basisverificatie wordt het wachtwoord in de vorm van leesbare tekst verzonden. Voor de beste beveiliging wordt geadviseerd de opties NTLM-verificatie en Alleen verbinden via SSL in te schakelen.

Oplossing:

1. Windows Verkenner
2. Ga naar Tools à Folders Options
3. Ga naar File Types Tap
4. Zoek XLS op

5. Klik op Advanced

6. Klik Edit

Pas de volgende regen aan: Application used to Form Action
Standaard: “C:Program FilesMicrosoft OfficeOffice12EXCEL.EXE” /e

Moet worden: C:Program FilesMicrosoft OfficeOffice12EXCEL.EXE” /e “%1″
7. Klik twee keer op OK
8. Klik op Close
9. Nu moeten 2003 Excel bestanden snel geopend worden.

Sinds Exchange 2007 uit is waren er al in bepaalde gevallen bekend dat men dubbele mailtjes kon binnen krijgen als je Outlook 2003 gebruikt om de afwezigheids assistent te gebruiken. In SP1 voor Exchange 2007 is dit probleem aangepakt. Er zijn sommige software pakketen die gebruik maken van OOF.
Als je meerdere versies van Outlook gebruikt om afwezigheids assistent te Configureren kan dit tot meest vreemde problemen ontstaan.
Als je een grootte lap tekst gebruikt in de afwezigheids assistent die je geconfigureerd hebt met Outlook 2007 of OWA 2007 en je wil dezen aanpassen in Outlook 2003 dan kun je de volgende melding krijgen.

Er is goed nieuws toch over te melden. Namelijk voor interne afwezigheids mailtjes zal dit zelfden voor komen. Dit zou wel kunnen voorkomen voor Externe afwezigheids meldingen maar die worden niet ondersteund in de Oudere Outlook versies.

Externe Afwezigheids meldingen worden overschreven door Interne meldingen.

Oudere versies van outlook hebben alleen een afwezigheids melding tekst vak. Dus je zit in Outlook 2003 dus alleen de interne afwezigheids melding in Outlook 2003. Waarneer je op OK in afwezigheids assistent klikt in Outlook 2003 wordt de externe en interne afwezigheids melding overschreven met de afwezigheids tekst zoals in de oudere Outlook versies. Het voordeel is wel als je op OK klik dat de externe afwezigheids assistent automatisch wordt uitgeschakeld.

Afwezigheids schema uitschakelen voor Outlook 2003

Als je afwezigheids schema gebruikt in Outlook 2007 of OWA 2007 dan krijg je meest rare problemen als je Outlook 2003 gebruikt om de instellingen aan t e passen.

Het eindresultaat is afhankelijk of de tijd van nu valt in Start & Eind tijd van de ingeschakelde afwezigheids assistent.

Regels zijn alleen aanpasbaar in de versie waarin ze zijn Aangemaakt.

Afwezigheids regels die aangemaakt zijn in Outlook 2007 zijn altijd zichtbaar in alle Outlook versies.
Regels kun je aanpassen aanzetten uitzetten in de versie welke zijn aangemaakt.

Conclusie,

Met Exchange 2007 OFF is dat je het beste Outlook 2007 of OWA 2007 gebruikt om afwezigheid instellingen te maken. Als je op OK klik in de oudere versie van Outlook worden sommige dingen aangepast (Uitgezet/aangepast) zonder dat je daar melding van krijgt. De enigste situatie is wanneer je in de oudere versie van Outlook niks aangepast wordt is als je een tekst gebruikt zonder enige opmaak.

Zorg er voor dat je de laatste Outlook versie gebruikt om de instelling aan te passen.

Oorspronkelijk document:

http://msexchangeteam.com/archive/2007/04/04/437544.aspx

Alleen tja hij moet geinstalleerd worden op 10+ pc’s dan doe je het volgende:
Pak een machine wellicht een VM en dubbel klik op licentie agreement en wacht er op dat hij deze uitgepakt heeft en klik vervolgens op OK. Ga vervolgens naar C:Program FilesMSECacheO2007Cnv1033 en kopieer vervolgende de uitgepakte files naar een netwerk schijf bijvoorbeeld ( \serverappsmsi packetsOffice2003fcv) waar alle domein users lees rechten op hebben vervolgens.

Maak een nieuwe GPO of edit een bestaande en koppel aan deze GPO O12Conv.msi. Hang aan deze GPO de juist pc’s/laptop’s en hij wordt automatisch uitgerold.