Category Archives: Windows Server 2008 R2
Its all about Windows Server 2008 R2 solutions & tricks…
Microsoft Outlook is prompting for User Password after Live Migration Failure | Live Migration caused DNS Resolution issue for Domain Controller VM | Hyper-V Live Migration Best Practices | Virtual Domain Controller Best Practices
Author: Zahir Hussain Shah | MVP Exchange Server, CISSP
Step by Step Troubleshooting of Microsoft Outlook Prompting for User Login Password, after a failed Live Migration of Domain Controller Virtual Machine, and the DNS Name Resolution Issues, while also discussing the Name Resolution and Domain Controller Best Practices for Virtualized Environments
With the above title of the post, we will also be discussing the following topics in the blog post:
- Hyper-V Live Migration Best Practices
- Virtualized Domain Controller Best Practices
- Domain Controllers and DNS Name Resolution Strategy in heterogeneous Domain Controller Environment
Recently, I came across an issue, where after a failed Live Migration of a Windows Server 2008 SP2 VM based Domain Controller (DC) on Windows Server 2008 R2 SP1 Hyper-V Server, caused serious problem for DNS Name Resolution, and since this Virtual DC was the primary DNS Server for all the Servers and clients, it also caused Microsoft Outlook to prompt the user passwords, whenever a user was opening Microsoft Outlook.
Problem: Live Migration Failure:
This Virtual DC was running on Windows Sever 2008 R2 Hyper-V Cluster, and at the time of performing Live Migration of this VM, the Live Migration failed at the source Hyper-V Server due to the fact that, VM was having an ISO image configured in the VM settings, which was located on the local C:\ drive of the Hyper-V host.
As a result of failing the Live Migration, VM stays at the same source Hyper-V Server, but its Virtual NIC settings got an error, and practically you can say that VM DC V-NIC association with the Hyper-V Physical NIC got broken, which resulted the VM lost connection to the Network.
Problem: Bad DNS Resolution and Microsoft Outlook Password Prompt for Users:
Okay, so we know now what happened to the DC VM, so to fix this problem without restarting the machine, I went to the VM properties, and set the Network to the same Hyper-V Virtual Network for the DC VM, and found that the VM came back online on the Network, so we were able to ping the DC, but later soon after that we found that Outlook users started complaining that, they are requested every time to provider user password, whenever they open Microsoft Outlook.
Nevertheless, as being a primary DNS Server and DC for authentication, after Live Migration Failure and resetting up of VMs network settings, it was noticed that, this DC as being a preferred DNS Server is no longer functional, means if you try to nslookup any name, it was getting failed, and also we found that the DNS Server service got stopped on the DC.
Okay now lets talk about Resolution to fix this problem, as its grown massively and affected all the clients and server for DNS Name Resolution and Outlook password prompts, which are quite annoying in nature.
Lets first discuss the Hyper-V Live Migration Best Practices:
I would recommend to always:
- Make sure that you dismount any ISO file attached to the Virtual Machine before hitting Live Migrate to other Hyper-V host, if your ISO file is not highly available, means if it cannot be accessed from the destination Live-Migration Hyper-V host.
- Your preferred DNS Server for Hyper-V Name Resolution and Authentication Server (DC) should bet set to the one, which is either on the different Hyper-V Cluster or Hyper-V Host, which will help you to be still in the game if your Live Migration fails or the DC VM fails.
- It would also be advisable to make sure that instead of pausing the VM, you always go for shutdown on Hyper-V, as a general good-practice.
Secondly to further discuss the above explained problems with regards to DNS Name Resolution and Microsoft Outlook password prompt for end-users, see the below guidelines:
Follow the steps to fix the problem in the order: (Note: We will try not to shut down the VM):
- After failing the Live Migration, the Network settings needs to bet setup correctly, means attaching the VMs NIC to the Hyper-V Virtual Network.
- Since now after doing the above setup, the VM will come on the Network, so either you can take RDP or from the Hyper-V Console, login into the VM, and try to START the DNS Server Service.
- After doing starting the DNS Server Service, you will see the NIC card of VM will be having a small warning sign, which will tell you that there is a problem with the Network Connectivity, so you can reset (Disable / Enable) the NIC of the VM.
- After the NIC resetting try to clear the DNS Cache and Register the machine in the DNS Server database, by ipchonfig /flushdns and ipconfig /registerdns.
So now, when you will open NSLOOKUP on the VM or on the other Servers / Clients, where this VM was having as preferred DNS Server, you will see the FQDN as the Server in the NSLOOKUP utility, and you can resolve the names.
Okay so now the DNS Name Resolution problem has been resolved, now we will go ahead and will try to fix the Microsoft Outlook password prompt issue, which caused due to the bad DNS Name Resolution issue:
You can follow the below steps to fix the Outlook password prompt issue:
Lets give a restart of one Exchange 2010 CAS Server at once, and once you will have both the Exchange 2010 CAS Server restarted, check for the below:
- Try to see the status of the Active Directory Replication, and give a repadmin /sycnall from the CMD with elevated administrative rights.
- Check for the Name Resolution from both Exchange 2010 CAS Servers.
- Since we didnt restarted the Exchange Mailbox Servers, try to go to them, and clear their DNS Cache and Register them back to the DNS Server with (ipconfig /flushdns, ipconfig /registerdns).
- o Everywhere you to make sure that you are able to resolve names, means the Server status at NSLOOKUP after the DNS Name Resolution steps performed, it should be okay.
- After giving the adequate time of AD Replication, you will find that Microsoft Outlook users are no longer asked for the password prompt, and they can open Outlook without any Windows Security dialog box.
Virtualized Domain Controller Best Practices:
In past, I published a blog post Best Practices for Running Virtualized Domain Controller, today in addition to all the best practices explained in that blog post, I would like to add the few down:
If your Primary DC (preferred DNS Server) is a Virtual Machine, always try to run it on a Standalone Hyper-V Server, because sometimes the failure of either the Hyper-V Cluster or DC VM can cause problem for either of them. I know Im saying for not to make DC VM Highly Available, but at the same time, I also seen from my practice experience, moving primary DC to Hyper-V Cluster will be a problem, when the enter Cluster is down, and when Cluster will try to come up where the DC (primary DNS Server) is not available, you could end-up with the cluster will not come online easily.
Try to virtualize the DC VM as an Additional Domain Controller but not for the primary and preferred DNS Server.
Domain Controllers and DNS Name Resolution Strategy in heterogeneous Domain Controller Environment
- As we said above, try to keep the VM based DCs (VM) as the secondary DNS Servers, because in some circumstances brining a VM based DC come online can cause problem for the entire environment, where brining an Physical DNS Server and DC is relatively handy, because all you need the network connectivity and the server should be up and running.
- From the prospective of bringing entire Datacenter down for some major power maintenance, it would be highly recommended to have Physical Domain Controller for all primary DNS Name Resolution and Active Directory Authentication needs.
I hope with the steps explained in this article, it will greatly help you to fix your DC Authentication and DNS Resolution issues after the failed Live Migration of DC VM, also you can take advantages of the various best practices outlined in this article for DNS Name Resolution Strategy and DC Virtualization for Hyper-V environments.
Cheers!
Export Print Server Queue (Printer Name, Driver, Port, IP Address) to CSV File | How to export Printer | Get Printer queue and port through Script (PS1) | Migrate Windows Print Server
Author: Zahir Hussain Shah, MVP Exchange | CISSP
Export your Print Server Queue Data to CSV
Recently I received a request to export Network Shared Printers queue related data from all our Windows Print Servers located in the different locations, to an MSExcel (CSV) file format, where this request also included vast majority of printer queue related data, including Printer IP Address (Port), Share Name, Location, Driver Version, and etc And when I looked at the native Windows functionalities to provide this information, then I come to know that Windows Server Print Management Console doesnt provide much information, especially for the Port Details (IP Address), which is the essential part of maintaining printer queue related data.
Well after doing some initial research, I came across a wonderful blog post from Christowles, for sharing a PowerShell Script for remotely gathering Printer queue data from Print Server using WMI.
This script will connect to the remote Windows Print Server over WMI protocol, and finds all the locally installed printer queues, and then export the below table filed data to CSV file to the printer script directory:
| NameAvgPagesPerMinute | Caption | Comment | Default | DriverName | JobCountSinceLastReset | Local | Location | Name | Network | PortName | PrinterStatus | PrintJobDataType | PrintProcessor | Shared | ShareName | Status | StatusInfo | SystemName | WorkOffline |
You can download this PowerShell script from my SkyDrive.
Okay, so now lets see how it grabs data remotely from Print Server:
1) Download the Script from my SkyDrive Account.
2) Execute the script from the Windows PowerShell (You can add PowerShell to Windows 7 with Windows 7 Administrative Tools).
3) Upon executing this script, it will ask you for the Server Name, provide the server name, so script will connect remotely to grab all the data for you.
Once data gathering will be done, it will notify you on the PowerShell screen about the exported CSV file in the script directory.
I hope you enjoyed reading this blog post, as it helps a lot to maintain the record about the network shared printers, and at the event of disaster for rebuilding the print server.
Securely Publishing iPhone with Microsoft Exchange Server 2010: Business Integration and Deployment
Book Review: Securely publishing iPhone with Microsoft Exchange Server 2010: Business Integration and Deployment
By Steve Goodman
Recently, I was requested to write a blog review for a book iPhone with Microsoft Exchange Server 2010: Business Integration and Deployment. This book is written by Steve Goodman, and published by Packt Publisher. Being an Exchange geek, after you read the title of this book, it really influences you, and pushes forward towards seeing the contents of the book, where this book doesnt have only the impressive title, but also have great contents for its readers, Steve laid out the content of the book in a pretty nifty way, where he is first explaining the architecture of the solution, and then he goes step by step to and covers all the areas, which are essential to build a secure enterprise level messaging environment for the corporate business users, and its integration with iOS devices (aka smart-phones) for Microsoft ActiveSync protocol.
Reading Steves write ups have always been interesting for me, as you can also find his blog in my blog-rolls area. You can get to know more about Steves community contribution on his blog.
Have you been tasked with getting iPhones into the hands of your business executives, and need to ensure they can reliably and securely access corporate e-mail? This book will teach you what you need to know about getting Exchange 2010 set up and then help you deploy iPhones in a secure and manageable way. Starting with the basics, you’ll learn about what Apple mobile devices have to offer and how they have evolved into devices suitable for business use. If you’re new to Exchange Server 2010, you’ll learn the basics of Microsoft’s world leading messaging suite, before learning how to plan, install, and configure a highly available Exchange
environment. You will also understand how to configure Office 365 and learn how both can be configured to apply policies to iPhone, iPad, and the iPod Touch. You’ll also learn how to configure advanced features, such as certificate authentication, how to create and deploy configuration profiles for devices, and how to manage your devices once they are in the hands of your users.
After reading this book, you will be confident about introducing Apple mobile devices into your organization.
Now lets go back to the book review, and let me break it in pieces:
Who this book is for:
This book is aimed at system administrators who don’t necessarily know about Exchange Server 2010 or ActiveSync-based mobile devices. A basic level of knowledge around Windows Servers is expected, and knowledge of smartphones and email systems in general will make some topics a little easier. Experienced Exchange Server 2010 administrators will gain most value from chapter five onwards, as these chapters build upon a working Exchange 2010 organization.
This book will walk you through from the basic of the technology towards the building an Exchange Server 2010 Messaging Infrastructure, and then will slowly move ahead with provisioning, integrating and deploying iOS based client devices (smart-phones) and their business collaboration feature management.
I thought it would be nice, if I can provide some information about the contents of the book, below is the list of the core domains, which will be discussed in his book.
Chapter 1, Introduction to iPhone with Exchange Server 2010 introduces the Apple mobile device range and Exchange Server 2010 starting with the fundamentals and explaining the concepts used in later chapters.
Chapter 2, Architecture and Implementation Planning covers planning the architecture that you will need in place for Exchange Server. You’ll learn about the individual Exchange Server roles and how to plan your underlying infrastructure so it not only allows Apple mobile devices to connect, but meets the needs of your company.
Chapter 3, Exchange Server Configuration for iOS Connectivity follows on from the planning in the previous chapter to walk through the process of installing and configuring a highly available Exchange infrastructure that Apple mobile devices, amongst others, can connect to.
Chapter 4, Office 365 Configuration for iOS Connectivity looks at an alternative approach to configuring and running Exchange Server, by using Microsoft’s Office 365. We’ll see how this simplifies the implementation process and still allows us to connect and manage Apple mobile devices.
Chapter 5, Creating and Enforcing Policies explores how Exchange Server allows us to control end-user devices, from restricting the features that can be used on Apple mobile devices to ensuring only allowed devices can connect to your Exchange infrastructure.
Chapter 6, Configuring Certificate Based Authentication in Exchange Server 2010 walks through how to configure and manage a small public key infrastructure aimed at improving the security of your Exchange environment through the use of user
certificates on Apple mobile devices.
Chapter 7, Provisioning iOS Client Devices introduces the iPhone Configuration Utility, the Apple tool specifically aimed at controlling Apple mobile device features and configuration, along with exploring the methods available to deploy profiles to mobile devices.
Chapter 8, Sharing Mailboxes and Calendars covers a variety of methods that allow you to overcome Exchange limitations for access to shared mailboxes from clients other than Outlook and how to configure advanced features in Exchange Server 2010 allowing users to share individual calendars in a way compatible Apple mobile devices.
Chapter 9, iOS Client Device Management the final chapter, explores the ongoing management tasks associated with a mobile device estate along with how to perform common troubleshooting and auditing tasks.
Few links:
Buy your copy of this book at Packt Publishing website.
I hope you enjoyed reading this review, and will find this book interesting.
Cheers!
Microsoft Exchange Server Mailbox Database LUNs are running out of disk space with hidden data | Delete System Volume Information (Disk Shadow) | Free-up Exchange Server Mailbox Database LUN (Disk ) | How Delete Shadow Copies
Author: Zahir Hussain Shah, MVP Exchange Server, CISSP
Recently, I saw a situation, where on the Exchange Server 2010 Mailbox Database LUNs (Disks) are running out of free-disk space, and upon inspection, we found that other than Mailbox Database and Logs folder, there is some hidden data, which is consuming the free-disk space, and it is not seen able, so I got to recall the Disk Shadows problem, for which I wrote an article (Exchange 2010 VMs on Hyper-V Server are stopped due to unavailability of free disk space | Hyper-V Server is running out of free disk space on the Server) in past, where using VSS based Backup tool is failing to delete the VSS snapshot files from the disk (volume), after successful or unsuccessful backup jobs.
Okay, so what is happening here, we will see in the following section:
Problem / Cause:
When you use VSS based backup tools, like Symantec Veritas NetBackup, which uses VSS to take the snapshot (backup) of the required data, and where sometimes due unsuccessful backup jobs, and file locking (antivirus cause) problem, in some circumstances, VSS backup tool / VSS Service fails to delete the temporary files from the Disk (LUN), or in other words, you can say that due to the failed backup jobs, VSS creates the snapshot temporary files in the DISK, and which over the time eats your available free disk space.
Symptoms:
If you want to see how these files look like, you can go to the drive, e.g. E:\ make sure the hidden files are unchecked, open System Volume Information, and there you will see all these temporary created files, like <99898-8888-xxxx-xxxx>.
Solution:
For bring this consumed free disk space, lets do the following for removing these Volume Shadow copies:
1) Open CMD with RUN AS ADMINISTRATOR
2) First list the available generated shadow copies by running the below command:
DISKSHADOW
Since now you are on DISKSHADOW prompt at command prompt, lets list all the available shadow copies by running the below command from the DISKSHADOW prompt:
LIST SHADOWS ALL
Upon running the LIST SHADOWS ALL command, you will see all the shadow copies, so then you can run the below command from the same DISKSHADOW command prompt for deleting these shadow copies:
DELETE SHADOWS ALL
And now you can go back to Windows Explorer, and can evaluate your available free disk space, and will glad to see that all your hidden consumed disk space is back now. 
I hope this will resolve your problem, and will help to stay relax from being tense to see your Hyper-V Servers (or any Server) physical disk free space getting consumed by hidden stuff.
Cheers!
Learning PowerShell | Microsoft Script Explorer | PowerShell Help | Exchange PowerShell Guide | Active Directory Scripts | Windows 7 PowerShell | SharePoint PowerShell | System Center PowerShell | SQL Server PowerShell
Author: Zahir Hussain Shah | MVP Exchange Server, CISSP
Learning PowerShell has never been so easy and fast… Try Microsoft Script Explorer for Windows PowerShell (pre-release)…
This is going to be my AWESOME post, where I will be sharing with you about a new learning and operations optimizing release by Microsoft, it is Microsoft Script Explorer for Windows PowerShell, the current version is pre-release, and it provides a handy way to search for PowerShell resources for the different Microsoft products, e.g. Exchange Server, Active Directory, and etc, it provides pre-cooked material, like Scripts, and cooking recipes, like How-to Guides for various TechNet library resources.
Download it now, and you can install this on your PC (Windows XP / Windows 7) or directly on the Server, on Windows 7 it requires .NetFrameWork 4.0, which you can download from here.
After some initial working with Microsoft Script Explorer for Windows PowerShell, it really found it as a good training and learning resource, where it provides you a easy way to get to the whole world of PowerShell and Scripts, and on the other end, it provides you a way to script most of your operations task, and get things done in a more automated fashion.
So get set go, and get your PowerShell Explorer today!, for more information about MSE, check out this link
Let me also share some of the snapshot of the MSE here…
I hope you will enjoy reading this post
Cheers!
Clear Submission Queue on Microsoft Exchange Server 2007 / 2010 | Remove message from queue on Hub Transport Server | Delete ambigous messages from submission queue | Emails are stuck in the Exchange Server queue | Troubleshooting Exchange Queue
Author: Zahir Hussain Shah | MVP Exchange Server, CISSP
Troubleshooting Microsoft Exchange HUB Transport Server (Transport Queues)
Often due to loss of Internet connectivity and DNS name resolution issues, we run into a situation, where we see a big count of e-mails get stuck at Exchange HUB Transport Server queue, usually these e-mails get stuck at your smart-host connector, which is the next-hop for your e-mails, but sometimes, due to some conflicts and other issues, we see e-mails get stuck in the Exchange Hub Transport Server for different queues, instead of the one, which is bound with your smart-host, for an example, lets say if you are using FOPE (Microsoft Forefront Online Protection for Exchange Online Service), then in this case, you will see emails getting stuck at mail.global.frontbridge.com (SmartHostConnectorDelivery).
Okay, we said something about the queues, now let me drive your attention towards the goal of this blog post, where I will guide you the basic troubleshooting for your Exchange Hub Transport Server and its queue.
Here are few of the common issues with Microsoft Exchange Hub Transport Server and its queues:
Problem:
1) E-mails get stuck at the SmartHostConnectorDelivery for out-bound e-mail delivery
2) Last Error: A matching connector cannot be found to route the external recipient
3) Last Error: 420 4.2.0 RESOLVER.ADR.Ambiguous; ambiguous address / Large number of messages get stuck at submission queue
Resolution:
E-mails get stuck at the SmartHostConnectorDelivery for out-bound e-mail delivery Issue:
For this type of problem, usually the cause is the loss of connectivity with Internet or with the HUB Site, which is responsible for routing e-mails to the appropriate destination (commonly to the Internet), and sometimes, it happens due to the bad DNS cache, which does not allow you to connect with the Smart-Host for the email delivery, and also the authentication which plays a vital part for allowing your HUB Transport Server to connect with remote-smart-host for delivering e-mails.
You can use the below solutions to fix this type of issues with e-mail delivery:
–>> Fix the IP connectivity issues for Internet / remote smart-host.
–>> Clear the DNS cache on DNS Servers and Exchange Hub Transport Servers (IPconfig /flushdns).
–>> Based on your remote-smart-host authentication requirements, set the appropriate authentication providers on your Send-Connector.
Last Error: A matching connector cannot be found to route the external recipient:
As it sounds with its name that the corresponding or matching send-connector is missing from Exchange HUB Transport Configuration, and for fixing this problem, you can create a send connector for the similar SMTP Address Space, but if you want to create a single SMTP connector for all type of domains, then make sure that you create *, a wild-card based SMTP connector, so all emails for any destination will be routed through this send-connector:
Last Error: 420 4.2.0 RESOLVER.ADR.Ambiguous; ambiguous address / Large number of messages get stuck at Submission Queue
This type of situation happens, when you perform some type of activity, which in result conflict the LegacyExchangeDN attribute on Exchange Server, (for reading more about legacyExchangeDN, read the below links), in this case, Exchange Server cannot decide where to send email for the particular legacyExchagneDN value, where the same value being used for either two different Mail-Enabled Users (Mailboxes) or between Mail-Enabled User (Mailbox) and Mail-Enabled Contact, in this situation, this emails will always stay at the Exchange Submission Queue, and you will constantly will receive the below errors in the Exchange Hub Transport Server event viewer:
Messages stuck at Submission Queue on Exchange Hub Transport Server:
Question: Okay, since these are ambiguous messages, which got created when there is a conflict of LegacyExchangeDN, now I have fixed it, so how can I remove these messages, because they are logging the above shown error log in me Exchange Hub Transport Servers event viewer?, well unfortunately, there is no way to delete messages from Exchange Management Console in both Exchange 2007 / 2010, and recently, while working for one case with Microsoft Support for Exchange Team, where I asked them can I delete these messages, so they told me the ONLY way to delete these ambiguous message from Exchange HUB Submission Queue, you have to Stop the Microsoft Exchange Transport Service, on Exchange Hub Transport Server, where the messages are stuck in the submission queue, and then rename the C:Program FilesMicrosoftExchange ServerV14TransportRolesdata” data folder to Data_OLD, and then start the “Transport Service”, which will recreate the “Data” folder, with fresh database for queue and other required files and folders, so this way you can delete these messages, and which sounded quite annoyed to me, that renaming these type of folders, is not a good idea, so I started looking for a solution, where I can delete these messages from Exchange Management Shell.
And a good thing that when I looked at the possibility for deleting these messages from EMS, so I found that it is pretty straight forward and easy, so lets see how you can delete them from Exchange Management Shell in both Exchange 2007 / Exchange 2010:
| [PS] C:Windowssystem32>Get-Queue -id Submission | Get-Message | Remove-Message -WithNDR $false |
Where in the above CMDLet WithNDR $false is telling the Exchange Server that dont send NDR to the original senders of the email, so you can scilently remove these messages from your Exchange without letting your end-users know.
In addition to the above CMDLet, you can use the same CMDLet for other queues, which are getting generate in your Exchange Hub Transport Server, for knowing about the Exchange Hub Transport Queue, you can run the below CMDLet:
| [PS] C:Windowssystem32>Get-Queue
Identity DeliveryType Status MessageCount NextHopDomain——– ———— —— ———— ————-Server_Name\Submission Undefined Ready 0 Submission Server_Name \Unreachable Unreachable Ready 1 Unreachable Domain |
To know more about LegacyExchangeDN, see the below links:
Update legacyExchagneDN attribute for Mail-Enabled Contacts
GAL Sync issues for LegacyExchangeDN
This blog post will enable you to manage and troubleshoot your Exchange Hub Transport Server and it’s queue efficiently.
Cheers!
Microsoft System Center 2012 Training | Cloud Computing Training | SCVMM 2012 | Hyper-V Training | Hyper-V Cloud Computing | Microsoft Private Cloud
Author: Zahir Hussain Shah | MVP Exchange Server, CISSP
Take a Cloud Journey, and Build your Career with Cloud Computing expertise!
In the month of January, 2012, I posted a blog article, in which I shared Step by Step Video Training for Building Microsoft Windows Server 2008 R2 Failover Cluster for Microsoft Hyper-V High Availability with Cluster Shared Volumes, this blog post provided a tremendous amount of information for building the Hyper-V Cluster on Windows Server 2008 R2 for making your VM work-loads Highly Available, which is a first-step for going forward with Cloud Computing, because Cloud Computing has always been expressed as a Journey, because it is not a product, which you just install in your network, and thats it, you have Cloud Computing now, but instead of this Cloud Computing is a world of Virtualization, Building Processes, Automation, providing Self-Service experience to your end-users, and efficiently using your computing resources, wherever and whenever you need them to provide different types of Cloud solutions with economics to your customers.
So without further putting texts here, lets directly jump straight towards the training, which will provide you end to end knowledge for building and running Microsoft Private / Public Cloud Computing solutions for you and your customers environment.
Recently, Microsoft arranged a online Microsoft Cloud Computing Jump-Start boot-camp, which took placed on Feb. 21-22, 2012, where the tons of tremendous knowledge transfer session conducted for Microsoft System Center 2012 family and Microsoft Cloud Computing offerings.
You can download or can watch all these sessions recording as follows:
Private Cloud Jump Start (01): Introduction to the Microsoft Private Cloud with System Center 2012
Private Cloud Jump Start (02): Configure & Deploy Infrastructure Components
Private Cloud Jump Start (03): Configure & Deploy the Private Cloud Infrastructure
Private Cloud Jump Start (04): Configure & Deploy Service Delivery & Automation
Private Cloud Jump Start (05): Configure & Deploy Application Management
Private Cloud Jump Start (06): Monitor & Operate Infrastructure Components
Private Cloud Jump Start (07): Monitor & Operate the Private Cloud Infrastructure
Private Cloud Jump Start (08): Monitor & Operate Service Delivery & Automation
Private Cloud Jump Start (09): Monitor & Operate Application Management
If you enjoy a 100-level strategic overview of the cloud, consider checking out this Cloud 101 Jump Start on March 13, 2012.
Let’s embrace the “Cloud”!
Update LegacyExchangeDN Attribute for Mail-Enabled Users / Contacts | LegacyExchagneDN attribute is missing from Mail-Enabled Contacts | Exchange Mail Contacts Problem | Emails are not going for Adress Book Contacts
Author: Zahir Hussain Shah | MVP Exchange Server, CISSP
Update and Populate LegacyExchangeDN Attribute for Exchange Mail-Enabled Contacts
This is my second blog post for the Microsoft Exchange Server Mail-Enabled Contacts, recently in my first blog post for the same subject, where we discussed the GAL Synchronization issues for Mail-Enabled Contacts using MIIS 2003 (Legacy IDM Solutions) with Windows Server 2008 Active Directory and Exchange Server 2010, and Troubleshooting the legacyExchangeDN attribute missing problems for Mail-Enabled Contacts, but here I will provide you some of the basic troubleshooting steps, which you can use as preliminary steps for troubleshooting your Exchange Mail-Enabled Contacts, and populate the necessary LegacyExchagneDN attribute for the Mail-Enabled objects, for the proper flow of emails to these Mail-Enabled Objects.
In my first blog post for this series, we performed some advance troubleshooting steps, because we saw that we were not able to populate the LegacyExchangeDN attribute for the Mail-Enabled Contacts, due to the high number for courrpted mail contacts, which were causing the Get-Mail-Contact resultsize unlimited | Set-Mail-Contact CMDLet to perform the operations, so therefore we had to use ADModify for forcefully appending the legacyExchangeDN attribute for these contacts.
This blog post will also help in the case, where you want to schedule the automatically updating and populating the LegacyExchangeDN attribute for newly created Mail-Contact by the legacy IDM Software, like MIIS 2003, which does not by default populate the LegacyExchangeDN, so what will be doing with the below CMDLets to first find out the ones, which doesnt have the attribute populated, and then we will generate the LegacyExchangeDN attribute for these newly created contacts.
Lets first find out, which are the newly created contacts, which doesn’t have LegacyExchangeDN attribute:
| [PS] C:Windowssystem32>Get-MailContact -ResultSize unlimited -OrganizationalUnit “ho.domain.com/GAL” -Filter { LegacyExchangeDN -eq $null } |
Lets assume that the above command provided a list of newly created contacts, which are out of legacyExchangeDN, so in this case, we would like to configure the LegacyExchangeDN attribute for them, so our Outlook users can send emails to them, and for achieving this, run the below EMS CMDLet:
| [PS] C:Windowssystem32>Get-MailContact -ResultSize unlimited -OrganizationalUnit “ho.domain.com/GAL” -Filter { LegacyExchangeDN -eq $null } | Set-MailContact |
I hope with this blog post, you will be able to fix your legacyExchangeDN population problem.
Cheers!
