The RTM versions of Exchange 2013, Lync 2013 and Office 2013 are now available on MSDN and Technet

Exchange 2013, Lync 2013 and Office 2013 RTM is now available for download on MSDN/Technet!!! Whoot!!!!!! Open-mouthed smile Open-mouthed smile Open-mouthed smile

MSDN Links:
Lync Server 2013 (x64) – DVD (English)
Exchange Server 2013 (x64) – DVD (Multilanguage)
Office Web Apps 2013 (x64) – DVD (English)
Office Professional Plus 2013 (x64) – DVD (English)
Office Professional Plus 2013 (x86) – DVD (English)
SharePoint Server 2013 (x64) – DVD (English)
Visio Professional 2013 (x64) – (English)
Visio Professional 2013 (x86) – (English)
Project Professional 2013 (x64) – (English)
Project Professional 2013 (x86) – (English)

Free E-book Deployment guide for Office 2013

 
This book supports a preliminary release of Microsoft Office 2013 and provides deployment instructions for Office 2013. The audiences for this book include application specialists, line-of-business application specialists, and IT administrators who are ready to deploy Office 2013.

Deployment-guide-for-Office-2013.pdf

Deployment-guide-for-Office-2013.doc

Deployment-guide-for-Office-2013.epub

Deployment-guide-for-Office-2013.mobi

578:0x000004DC:0x0000001D Send-As permission with Outlook 2010 Exchange 2007

578:0x000004DC:0x0000001D Send-As permission with Outlook 2010 Exchange 2007
Error:

myaddress@mydomain.com
You are not allowed to send this message because you are trying to send on behalf of another sender without permission to do so. Please verify that you are sending on behalf of the correct sender, or ask your system administrator to help you get the required permission.

Diagnostic information for administrators:

Generating server:

myaddress@mydomain.com

#MSEXCH:MSExchangeIS:/DC=com/DC=mydomain:SERVERNAME[578:0x000004DC:0x0000001D] #SMTP

Solution:
1.Close Outlook

2.Delete the offline address book folders in

Windows 7: C:\Users\username\AppData\Local\Microsoft\Outlook\Offline Address Books
Windows XP: C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Outlook\Offline Address Books

3.Open Outlook and let it download a new copy of the offline address book.

3.1 Send/Receive Tab
3.2. Send/Reveive Groups
3.3 Download Address Book
3.4 Choose Full Details and \Global Address List

VMware View XP persistent disk can not save outlook.ost c:\document and settings\…..

I’m busy with created a new a new pool with presentment disks.

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

GAL Photos in Exchange 2010 and Outlook 2010

With Microsoft Exchange 2010 and Outlook 2010 & Lync & Sharepoint 2010 you can finally get photos into your global address list (GAL) and see just who’s who on your emails. You can do this on 2 way’s

1. Using Powershell Smile

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

      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

        image image

      Autodiscover failed on Outlook 2007 client with error 0x800c8203 after installing KB2412171

      After installing KB2412171 on client computers I found another bug in this update.
      Normally Outlook configure your Outlook profile on your primarily smtp address. But after this update this is changed to the user principal name. If you have not added user principal name to a mail user you will see dat autodiscovery wil fail.

      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

      Deploy office 2010 and a previous office version together on one PC with MDT 2010

      Deploy office 2010 and  a previous office version together on one PC with MDT 2010. Then you need to do the following things

      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
      imageimage
      imageimage

      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.

      imageimage
      imageimage
      image

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

      Exchange 2010 Exchange Server name appears as Instance – <GUID>

      Current Status: Issue – no issue

      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

      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

      Translate »