Ensure that the server is connected to the internet and that “crl.microsoft.com” is resolvable using NSlookup ( If you got the warning while having internet connection )
If your server have no internet access , you can disable checking for publisher’s certificate revocation via Internet Explorer options ( see below )
Windows Server 2012 is the upcoming release from Microsoft for servers OS . On June 20-21, 2012 , Microsoft Learning partnered with the Microsoft Server and Tools team and Developer and Platform Evangelism (DPE) delivered the “Windows Server 2012 Jump Start: Preparing for the Datacenter Evolution” .
By now Microsoft announced that the HD-quality video recordings available on TechNet Videos !
Here are the links for the Videos on TechNet :
- Windows Server 2012 Jump Start (01): Core Hyper-V
- Windows Server 2012 Jump Start (02a): Virtualization Infrastructure, Part 1
- Windows Server 2012 Jump Start (02b): Virtualization Infrastructure, Part 2
- Windows Server 2012 Jump Start (03a): Storage Architecture, Part 1
- Windows Server 2012 Jump Start (03b): Storage Architecture, Part 2
- Windows Server 2012 Jump Start (04): Continuous Availability
- Windows Server 2012 Jump Start (05a): Multi-Server Management, Part 1
- Windows Server 2012 Jump Start (05b): Multi-Server Management, Part 2
- Windows Server 2012 Jump Start (06a): Security and Access, Part 1
- Windows Server 2012 Jump Start (06b): Security and Access, Part 2
- Windows Server 2012 Jump Start (07): Remote Connectivity and Networking
- Windows Server 2012 Jump Start (08): IIS, DHCP and IPAM
Whether you watched it online or downloaded it , you will be totally pleased with the content ; Enjoy
As posted earlier here for OCAT version 1.0 , the second version of Outlook Configuration Analyzer Tool (OCAT) provides a quick and easy method to analyze your Microsoft Office Outlook profile and mailbox for common configurations that may cause problems in Outlook. This can be very useful for busy Help Desk personnel when end-users call for help with Outlook or when you want to identify possible issues with Outlook proactively.
This release includes a lot of enhancements such as :
Automatic downloading of new detection rules : Allows updates from Microsoft for error detection /information gathering rules
Automatic downloading of OCAT installation files : All OCAT application fixes will be automatically detected upon connecting to internet and prompt admin for download
Addition of the CalCheck tool : The magnificent CalCheck command line tool which used for problems with Outlook calendars issues is now embedded with OCAT V2.
Addition of new detection rules : Around 75 new detections rules we added since OCAT V1
Improved support for Outlook 2003 : Some enhancements were added for Outlook 2003 support
Command-line version of OCATcmd.exe : A command line version of OCAT V2 that can be used by admins to scan computers in their organizations [ Check OCAT v2 supplemental information for how to use OCATcmd.exe ]
You can get both OCAT V2 and OCAT v2 supplemental information from here
One of my workmates was testing migration form Exchange 2007 to Exchange 2010 SP2 with multiple sites scenario , when he came with an issue with Exchange 2010 OWA to Exchange 2007 proxing.
Although Exchange 2007 CAS – located at remote site – doesn’t have an external URL for OWA and authentication method was set to integrated , accessing of a remote site mailbox failed with the following error message :
By examining the application event log on Exchange 2010 CAS an error was found at application log indicating the problem and gives the clue for solving it.
Log Name: Application
Source: MSExchange OWA
Date: 6/21/2012 11:57:07 AM
Event ID: 46
Task Category: Proxy
Client Access server "https://ex2010-01.itguydiaries.net/owa", running Exchange version "188.8.131.52", is proxying Outlook Web App traffic to Client Access server "Ex2007-05.itguydiaries.net", which runs Exchange version "184.108.40.206". To ensure reliable interoperability, the proxying Client Access server needs to be running a newer version of Exchange than the Client Access server it is proxying to. If the proxying Client Access server is running a newer version of Exchange than the Client Access server it is proxying to, the proxying Client Access server needs to have an Outlook Web App resource folder (for example, "<Exchange Server installation path>)\ClientAccess\owa\8.0.498.0" that contains all the same versioned resource files as the Client Access server it is proxying to. If you will be running Outlook Web App proxying with mismatched server versions, you can manually copy this resource folder to the proxying Client Access server. After you copy this resource folder to the proxying Client Access server, you need to restart IIS before proxying will work.
This is a common issue – here is a KB describes the issue for Upgrading Exchange 2007 to Exchange 2007 SP1 – which occurs because the Internet-facing CAS does not have the same Outlook Web Access control directory as the internal-facing CAS when a user is directed to another CAS through a proxy. It is common to happen , as it is recommend by Microsoft to always update the Internet-facing CAS first. Then, update all other CASs in the organization.
To solve this issue all we need do is to copy OWA control folder from Exchange 2007 server [ highlighted below ]
Add ( paste ) it at Exchange 2010 CAS [ C:\Program files\Microsoft\Exchange Server\V14\ClientAccess\OWA ]
By now , proxing works just as it should and remote site mailbox is normally accessible.
You may be familiar with the traditional ways to transfer FSMO [ Flexible Single Operation Masters ] roles but how about by using PowerShell ? By now you should just know that PowerShell can do everything the GUI can do … well at least that is the way it feels to me.
As we know that we have five operation masters as listed below [ Two per Active Directory forest ( 1,2 ) and three per Active Directory domain (3,4 and 5 ) ]
- Schema Master
- Domain Naming Master
- Domain PDC Emulator Master
- Infrastructure Master
- RID Master
In order to assist admins with FSMO moving I have made a simple script which simplifies the moving of FSMO.
All you need is to pick the option represents the operation master you want to move and assign a target domain controller and all is done.
In addition , I have added an option that allowed you to move all operation masters in a single action ( Option 7 ) and another option to query for the Operation Masters holders ( Option 1 ) .
One of our customer asked me about how he can set Outlook anywhere – RPC over HTTP – settings for all of his company users.
I simply answered that the best way to perform this action would be using of group policy with Office 2010 administrative templates . We just downloaded Office 2010 Administrative Template files , imported it using Group Policy Management Console ( GPMC ).
Upon looking for Outlook Anywhere settings all what we can found was “Configure Outlook Anywhere user interface options”
After a fast search I found this KB from Microsoft , which indicates that Outlook Anywhere policy settings are not included in the Group Policy template file (Outlk14.adm). !!
What you need to do is to download a separate .adm template that includes Outlook Anywhere settings , import it using GPMC and then the following settings for Outlook Anywhere will be feasible :
- RPC/HTTP Connection Flags
- Proxy Server Name
- Only connect if Proxy Server certificate has this principal name
- Proxy authentication setting
Just at this stage we were able to set Outlook Anywhere configuration and pass it to all company users’ Outlook
This Community Technology Preview (“CTP2”) enables System Center customers to jointly evaluate System Center 2012 and Windows Server 2012 Release Candidate. CTP2 includes updates and enhancements to the following System Center 2012 components:
- Virtual Machine Manager
Improved Support for Network Virtualization
Extend the VMM console with Add-ins
Support for Windows Standards-Based Storage Management Service, thin provisioning of logical units and discovery of SAS storage
Ability to convert VHD to VHDX, use VHDX as base Operating System image
- Configuration Manager
- Support for Windows 8
- Support for Mac OS clients
- Support for Linux and Unix servers
- Data Protection Manager
- Improved backup performance of Hyper-V over CSV 2.0
- Protection for Hyper-V over remote SMB share
- Protection for Windows Server 2012 de-duplicated volumes
- Uninterrupted protection for VM live migration
- App Controller
- Service Provider Foundation API to create and operate Virtual Machines
- Support for Azure VM; migrate VHDs from VMM to Windows Azure, manage from on-premise System Center
- Operations Manager
- Support for IIS 8
- Monitoring of WCF, MVC and .NET NT services
- Azure SDK support
- Additional support for Integration Packs, including 3rd party
- Manage VMM self-service User Roles
- Manage multiple VMM ‘stamps’ (scale units), aggregate results from multiple stamps
- Integration with App Controller to consume Hosted clouds
- Service Manager
- Apply price sheets to VMM clouds
- Create chargeback reports
- Pivot by cost center, VMM clouds, Price sheets
- Server App-V
- Support for applications that create scheduled tasks during packaging
- Create virtual application packages from applications installed remotely on native server