Category: Office

Microsoft Assessment and Planning (MAP) 6.0 Beta: Accelerate the adoption of Microsoft private and public cloud platforms

Planning your journey to the cloud just got a bit easier. The next release of the Microsoft Assessment and Planning (MAP) Toolkit—version 6.0 Beta—includes assessment capabilities to evaluate workloads for both public and private cloud platforms. With MAP 6.0 Beta, you now have the ability to identify workloads and estimate the infrastructure size and resources needed for both Windows Azure and Hyper-V Fast Track. Also new to MAP 6.0 Beta is the Office 365 client assessment, enhanced VMware inventory, and Oracle schema discovery and reporting. Expanded assessment and discovery capabilities from MAP help you streamline planning for your next migration project. Plan what’s next with MAP.

New features and benefits from MAP 6.0 Beta release help you:

· Analyze your portfolio of applications for a move to the Windows Azure Platform

· Accelerate planning to private cloud with Hyper-V Cloud Fast Track onboarding

· Identify migration opportunities with enhanced heterogeneous server environment inventory

· Assess your client environment for Office 365 readiness

· Determine readiness for migration to Windows Internet Explorer 9

· Discover Oracle database schemas for migration to SQL Server

Download the beta materials on Connect:http://go.microsoft.com/fwlink/?LinkId=219165

Microsoft Office 365 Deployment Readiness Tool

The Office 365 Deployment Readiness Tool provides analysis of your on-premises environment in preparation for an Office 365 enterprise deployment. The readiness tool is integrated with the guidance provided in the web edition of the Microsoft Office 365 Beta Deployment Guide.

Download HERE

I run the tool in my test environment. See below the results

Microsoft Office 365 Deployment Readiness Tool

Beta

Office 365 Deployment Resource Kit build 01.00.00.00
modgClick here for the Microsoft Office 365 Beta Deployment Guide for Enterprises

Domains

modg Deployment Guide: Adding Your Domain(s) to Office 365
All email domains discovered in your environment:
Total: 3

All primary email domains discovered:
Total: 2

Primary email domain suffixes with greater than 50 users:
wardvissers.local
Total: 1


User Identity and Account Provisioning

Active Directory

Statistics

Total number of domains discovered in your forest: 1
Estimated total number of users: 59
Estimated total number of contacts: 0
Estimated total number of groups: 54
Estimated total number of mailboxes: 53
Estimated total number of objects for Directory Synchronization: 113
note
Note: Filters were applied to obtain the above object counts for an Office 365 deployment.

Forest and Domains

The following domains were discovered in your Active Directory forest:
wardvissers.local
Total: 1

Trusts

No forest trusts found
green
You may deploy AD FS 2.0 and Directory Synchronization without multi-forest constraints

Schema and Forest/Domain Functionality Levels

Active Directory forest schema level: Windows Server 2008 R2
Exchange schema level: Exchange Server 2010 SP1
Domain Functionality:Windows Server 2008 R2
Forest Functionality:Windows Server 2008 R2
Domain Controller Functionality:Windows Server 2008 R2
green
It appears that your Active Directory schema is prepared for Exchange Rich Coexistence
modg Deployment Guide: Exchange Rich Coexistence Requirements


Active Directory Cleanup

modg Deployment Guide: Active Directory Cleanup

samaccountname (user name) Attribute

green
Character length test passed
green
Unsupported character test passed

givenname (first name) Attribute

green
Character length test passed
green
Unsupported character test passed

sn (last name) Attribute

green
Character length test passed
green
Unsupported character test passed

displayname Attribute

green
Character length test passed
green
Unsupported character test passed

mail (email address) Attribute

green
Character length test passed
green
Unsupported character test passed
green
No duplicates found

mailnickname Attribute

green
Character length test passed
green
Unsupported character test passed

proxyaddresses (email addresses) Attribute

green
No duplicates found
green
Unsupported character test passed

Directory Synchronization

Object count assessment:
Estimated number of objects for Directory Synchronization (entire forest): 113
modg Deployment Guide: Object Count Considerations
Enterprise Admin rights:
green
It appears that you are an enterprise admin
Directory Synchronization admin requirement met!
modg Deployment Guide: Directory Synchronization Required Permissions
Active Directory recycle bin:
warning
Active Directory recycle bin is enabled in your forest this may impact your total object count quota for Directory Synchronization.


Office 365 Single Sign On and Identity

AD FS 2.0 Directory Cleanup Check:

UserPrincipalName (logon ID for Office 365) Attribute

fyi
Update values once you have verified your organization does not have any other application dependencies on the UserPrincipalName attribute.
modg Deployment Guide: Active Directory Cleanup
green
Unsupported characters test passed
green
Spaces in logon value test passed
green
Unicode character test passed
note
Note: All Unicode characters will be converted to underscores (_) in the UserPrincipalName field.
green
No UserPrincipalName duplicates found
warning
Discovered users without a user logon name (blank value) for UserPrincipalName
You will need to provide each user a UserPrincipalName in order for these users to sign into Office 365.
fyi
Below is a list of your UserPrincipalName domain suffixes in use:
wardvissers.local
Total: 1
note
Note: During the Office 365 Beta only one namespace (root and child domains) per AD FS 2.0 farm
Example contoso.com and root.contoso.com would require 1 AD FS 2.0 farm and fabrikam.com would require an additional AD FS 2.0 farm

fyi
Password length per domain:

wardvissers.local = 7

Exchange Online

Discovered Exchange Server(s) on-premises:
Estimated total number of Exchange Servers: 1

Statistics:
Estimated total number of users with default mailbox size (True): 53
Estimated total number of users with larger than default mailbox size (False): 0
Estimated total number of objects with Exchange organization level quota: 6


Lync Online

Lync user assessment:
Estimated total number of users leveraging Office Communications/Lync on-premises: 2
Sip domains:
fyi
The following sip domains were discovered:
wardvissers.local
Total: 1

SharePoint Online

User object count assessment:
green
The number of user objects in your forest is supported.
modg Deployment Guide: Object Count Considerations

Client and End User Experience

modg Deployment Guide: Rich Experience Client Requirements

Summary of client computer readiness (Office 365 single sign-on and rich client checks):

warning
Below is an estimate of computer operating systems NOT ready for Office 365 rich client experience:
Total: 0
green
Below is an estimate of computer operating systems ready for Office 365 rich client experience:
Windows XP Service Pack 3: 3
Windows 7 Service Pack 1: 3
Total: 6

Network


fyi
IP Configuration:
IPv4 Address. . . . . . . . . . . : 192.168.150.60
IPv4 Address. . . . . . . . . . . : 192.168.150.1
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Default Gateway . . . . . . . . . : 192.168.150.254

fyi
Trace route to your default gateway:
Tracing route to 192.168.150.254 over a maximum of 30 hops
1 1 ms 2 ms 2 ms 192.168.150.254

fyi
Trace Route test to Exchange Online:
Tracing route to outlook.com [65.55.94.40]
over a maximum of 30 hops:
1 3 ms 2 ms 1 ms 192.168.150.254
2 * 24 ms 25 ms 82.169.11.254
3 25 ms 26 ms 26 ms 195.69.145.20
4 145 ms 146 ms 144 ms 10.14.234.234
5 * * * Request timed out.
6 * * * Request timed out.
7 10.14.234.234 reports: Destination net unreachable.
Trace complete.
fyi

For additional tests utilize the Exchange Remote Connectivity Analyzer

Port Query Tests:

modg Deployment Guide: Ports and Protocols
green
portal.microsoft.com
Made a TCP 443 connection to portal.microsoftonline.com
green
Outlook.com
Made a TCP 443 connection to outlook.com
green
Outlook.com IMAP
Made a TCP 993 IMAP connection to outlook.com
green
Outlook.com POP
Made a TCP 995 POP connection to outlook.com
green
Outlook.com SMTP
Made a SMTP TCP 587 connection to outlook.com
green
Active Directory Federation Services End Point
Made a TCP 443 connection to nexus.microsoftonline.com
green
Directory Synchronization End Point
Made a TCP 443 connection to adminwebservice.microsoftonline.com
green
Office 365 PowerShell End Point
Made a TCP 443 connection to ps.microsoftonline.com
green
Outlook.com PowerShell End Point
Made a TCP 443 connection to ps.outlook.com
green
Office 365 Community End Point
Made a TCP 80 connection to community.office365.com
green
Lync Online SIP Connection
Made a TCP 443 connection to sipdir.online.lync.com
green
Lync Online Federation
Made a TCP 5061 connection to sipfed.online.lync.com
Domain Name System (DNS) name records checks:
fyi
Found the following MX DNS record(s):
Server: localhost
Address: 127.0.0.1
wardvissers.local
primary name server = ward-dc01.wardvissers.local
responsible mail addr = hostmaster.wardvissers.local
serial = 761
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
Information Gathered On:
WARD-DC01
Date: za 07-05-2011
Start Time: 18:19
End Time: 18:21

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

      Add a MSN user to Lync Online & Office 365

      Today I have a relax day working from home . I have some time to play with Office 365 & Lync Online Open-mouthed smile

      I wonderd if there was a way to add a msn user to my Lync while using Lync Online.

      I added my own msn account on lync. On MSN Messenger I get the qwestion if I want to add a new contact. Yes off course… Smile

      Tada…. You can add all your MSN friends to Office 365 or Lync Online Open-mouthed smile

      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

      Free E-Book: First Look Microsoft Office 2010

      Katherine Murray has written a nice e-book about Office 2010: here it is (in XPS) and here it is (in PDF). 14 chapters 😀
      9780735693876f_thumb

      Deploy Office 2010 with Multiple Languages with MDT 2010

      I Like Office 2010. For me it is the best Office version i ever worked with.
      MDT 2010 it’s great tool that Microsoft created.
      Now i will talk about how you deploy Office 2010 with Multilanguage packs with MDT 2010.

      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.

       image

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

      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

        Translate »