Disappearing NetApp LUNs when moving to EMC?
by Scott on Mar.10, 2010, under EMC, Exchange Server, Microsoft Related, NetApp, Storage, Windows 2008
I was at a client site yesterday in the process of moving them off a NetApp Storage array and onto EMC Storage. My colleague and I ran into a very interesting problem and have no idea why it was happening. If anyone has any ideas please, do share.
The setup was two Windows 2008 Servers with Exchange 2007 CCR split between two datacenters. The servers were using Snap Manager for Exchange and Snap Manager. There were four LUNs from the NetApp presented, three for databasae and one for the logs. The LUNs were attached via iSCSI.
Since the Exchange CCR environment was running in the HQ Datacenter we started by getting the EMC agents installon the the Server in the DR Datacenter. The iSCSI LUNs from the NetApp were presented via Drive letters, there were four, three for the database and one for the logs. If you’re not familar with deploying EMC apps the first app to deploy is the EMC NaviHostAgent. When I installed the agent the server requested for a reboot. This is where things got really funky. When the server came back from a reboot the iSCSI disk drives from the NetApp were gone! No idea why. We scratched our heads and couldn’t figure out what happened. According to the NetApp management console the LUNs were presented. When we tried to remap the LUNs via Snap Manager it would state that the volume was already mapped to a drive on the server, but the Server could not see them! This was odd. We backed out the EMC NaviHostAgent and the LUNs reappeared but the drives were off line. I brought the drives back on line and everything worked again.
We then started by reinstalling the EMC NaviHostAgent, no reboot was required this time and installed the EMCPowerPath application. When we came back from a reboot the drives from the NetApp were off line again, I brought them back on line and had both the EMC and the NetApp storage provisioned. Great, this is nice. We presented the EMC LUNs as mount points and started up replication again from the HQ Exchange Server. Once replication was caught up moved the cluster to the DR server to begin the same process on the HQ server thinking we had a fluke.
Well, the exact same thing happened! When we installed NaviHostAgent no reboot was required. We then installed PowerPath, Had to reboot the server and the NetApp LUNs vanished! WTF right? Not again! We did the same procedure I mentioned above, removed PowerPath, removed NaviHostAgent, rebooted the Server in HQ. When it came back the NetApp LUNs were gone! No drive letters, no detection. Checked the iSCSI Initator configuration, and it was perfect, it was seeing the iSCSI targets for both the NetApp and the EMC. From the NetApps perspective the LUNs were provisioned. What in Windows 2008 was preventing the LUNs from being seen? I checked the Network settings via IPCONFIG and there was a “Local Area Connection 9″ that was there along with a Prod network and a iSCSI network. Looking at the network configuration only two NICs were active for the machine. No idea where the third NIC was coming from and by this time I was too tired to try to figure it out. Anyone out there have thoughts on that one?
Anyway, after troubleshooting for about 5 hours between the two servers I proposed a Plan B. Since we had the NetApp storage (Thank God) and the EMC storage on the DR server I could create new Storage Groups and Databases on the DR server to the new EMC LUNs. Create new EMC LUNs on the HQ Exchange Server to reflect what was in DR and let CCR take care of the rest. Once the Storage Group and Databases were created I enabled replication only for the EMC Storage Groups (since the NetApp was off line on the HQ Server I couldn’t re-enable CCR) and started moving mailboxes. This worked fine, disaster averted.
I was glad Plan B worked, but more complexing is why did the NetApp LUNs disappear? Anyone have an idea what may have happened with it? Again this was a Windows 2008 Server with Exchange 2007. The iSCSI network was correct, the NetApp was presenting the LUNs, when going into snap manager the LUNs said they were mapped. I tried to do a rescan of disks, nothing. Tried to take away the LUN and remap the LUN via NetApp management console and nothing worked. The Windows Firewall was turned off, disabled AV Software, nothing worked. Nothing would bring those LUNs back to the Windows 2008 server. Has anyone seen anything like this? Anyone have an idea on what happened? Please do share!
Thanks,
Update Rollup 2 for Exchange Server 2010
by Scott on Mar.05, 2010, under Exchange Server, Microsoft Related
The Microsoft Exchange Team has announced the release of Update Rollup 2 for Exchange Server 2010. For the announcement go here: http://msexchangeteam.com/archive/2010/03/05/454155.aspx
Some key fixes are:
For more information on the Hotfix you can go to the page at http://support.microsoft.com/?kbid=979611.
Enjoy!
Looking for a Good Skate Sharpener?
by Scott on Mar.02, 2010, under General
If anyone out there is like me and getting skates sharpened weekly or twice a week I would encourage you to take a look at the Wissota Skate Sharpener. I recently purchased one a few weeks ago and have enjoyed it ever since. My son who plays hockey is getting his skates sharpened at leased once if not two times a week and the run to the skate shop not to mention the $5 a visit was getting costly. According to the Wissota Web site it costs about 17 cents, yes $0.17 to sharpen one skate. Can you say savings? Well, insert the Wissota Skate Sharpener. The machine is pretty easy to use. I think the hardest part for me was to locate the crown. That’s the point where the wheel on the sharpener will hollow out a good radius. Yes, I’ve been reading up on Skate Sharpening. Once there I am now able to sharpen my skates and my sons skates any day and time and it takes only a few minutes. Much better then dropping them off at the skate shop and waiting hours, if not a day…..
Anyway, If anyone out there is looking for a good skate Sharpener I recommend the Wissota Skate Sharpener. I was able to to go to the company and pick up mine but they do ship. While I was there I got a great demonstration on how the machine worked and the Sales guy even gave me more instruction then I could possibly ask for. There is an instructional DVD included with the Machine along with a lot of extra pieces. I didn’t have to buy any thing more to get the machine to work.
So, if you are looking for a skate sharpener take a look at their web site, Wissota Manufacturing Company. And no, I’m not getting paid for this or getting something for free. I am happy with their product and wanted to recommend it to anyone out there Looking for a good Skate Sharpening Machine.
Move Root Certificate Authority from Windows Server 2003 to Windows Server 2008
by Scott on Mar.02, 2010, under Microsoft Related
Well, I’ve been trying to write this article for about a month now and finally had some time to sit down and type it out. I was inspired by this article when I had a client request to move their Root Certificate Authority on a Windows 2003 Domain Controller to a new Windows 2008 Domain Controller. To be honest, there really isn’t anything to it but the information I found out on the net wasn’t that great so I thought I would provide the world with some info on how to perform this process.
The Client setup involved a Windows 2003 domain controller that was acting up. On this DC was their Root Certificate Authority for their entire Active Directory environment. The client is small and does not have any special requirements for an Enterprise CA and wanted to move their CA to Windows 2008 Active Directory Certificate Services.
The key principles here are that we need to move the private key associated with the Root Certificate Authority and also the Certificate Authority Database. When moving a certificate Authority we need to preserve the CA name in the environment, otherwise nothing will work! The clients will not be able to locate the CA nor will the Root certificate match up with the certificates. Things just won’t be trusted.
To get started I reviewed the Support Article on How to move a certification authority to another server to backup the existing Windows 2003 Root CA Info. I first used the Certificate Authority snap-in to backup the CA database and private key. To perform the backup follow these steps:
- In the Certification Authority snap-in, right-click the CA name, click All Tasks, and then click Back up CA to start the Certification Authority Backup Wizard.
- Click Next, and then click Private key and CA certificate.
- Click Certificate database and certificate database log.
- Use an empty folder as the backup location. Make sure that the backup folder can be accessed by the new server.
- Click Next. If the specified backup folder does not exist, the Certification Authority Backup Wizard creates it.
- Type and then confirm a password for the CA private key backup file.
- Click Next, and then verify the backup settings. The following settings should be displayed:
- Private Key and CA Certificate
- Issued Log and Pending Requests
- Click Finish.
Next we have to save the registry settings. To save the registry settings perform the following:
- Click Start, and then Run. In the Run field type regedit and click Ok
- Locate and then right-click the following registry subkey, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration (While you are here, why not take a look at the settings, take a screen shot, make sure they match up in the end)
- Click Export
- Save the Registry file in the CA Backup folder that was defined above
Now that we have the database, certificate and registry backed up the next step was to remove Certificate Services from the old computer. This process is pretty straight forward. Go into the Control Panel, Add/Remove Programs, Windows Components and remove the Tick from Certificate Authority. Note Be sure to remove the Certificate Authority from the old computer prior to deploying Certificate Services on the new machine. If you deploy AD CS first the target CA will become unusable.
Finally, rename the old server or permanently disconnect it from the network.
In the step above I took the existing Domain Controller, removed the Certificate Services from it and then performed a DCPromo to remove Active Directory from the computer. Once the computer was no longer a domain controller I renamed the old server. I wanted to keep the server online for a fail back just in case, which wasn’t necessary since the move went over successfully!
Now, looking at where we stand right now I had the database, the Private Key and the certificate authority database backed up. The data I backed up above should be copied to the new server that will be used for Active Directory Certificate Services. This will need to be imported below. Now, the next step is to deploy Active Directory Certificate Services on the Windows 2008 domain controller. BTW I should point out that when deploying Active Directory Certificate Services that you should use Windows 2008 Enterprise edition. W2K8 Enterprise gives you more functionality of your Certificate Services. For a list of features in Windows 2008 Standard vs Windows 2008 take a look at this link: Active Directory Certificate Services Step-by-Step Guide. If you scroll down a bit you will see a comparison chart which will note which features are available with which version of Windows you use.
Now, let’s move on to the part where we deploy and restore the Certificate Services. Log on with local or enterprise administrator permissions to the CA computer and perform the followign:
- Launch the Service Manager for Windows 2008.
- In the console tree, click Roles.
- On the Action menu, click Add Roles.
- If the Before you Begin wizard appears, click Next.
- In the list of available server roles, select the Active Directory Certificate Services check box, and click Next twice.
- Make sure that Certification Authority is selected, and click Next. (Note: If you are going to use Web Enrollment make sure to check this box. You can always add it later but Why not add it now? All the required roles will also be installed when you check this box since you will get a list of Add role service required)
- Select Enterprise and click Next. (We are doing this because this is an Enterprise Root CA that will integrate with Active Directory. Just like the one I decommissioned. Best practice is to have a Standalone Root CA but given the size of this organization they are not too concerned with having a Standalone Root CA.)
- Specify Root and click Next. (If the CA you’re moving from was a Subordinate CA then we would want to tick the Subordinate CA option. But since in my example this is a Root CA we are sticking with root. Keep in main that if you’re coming from a Root CA or a Subordinate CA this option must match with what you’re coming from.)
- At this stage, you have a choice between creating a new private key or using an existing private key. For a migration, on the Set Up Private Key page, select Use existing private key and choose Select a certificate and use its associated private key.
You should have something that looks like this:
Click Next and continue the steps below:
- If the CA certificate we backed up above has been installed on the computer, it will be listed in the Certificates box. Otherwise, click Import to import a certificate from the .pfx file created by exporting the CA certificate and private key from the source CA.
- Click Browse, and locate and select the file containing the certificate and private key exported from the source CA.
- Enter the password you selected when exporting the CA certificate and key from the source CA, and click OK. Select the Certificate that was just imported and click Next
- When choosing your path you can either use defaults or browse to new ones. Once done click Next
- Complete the installation of the AD CS
- Click Yes to accept the warning to overwrite AD DS. (This appears only if you are installing an enterprise CA.)
Congratulations, you’re almost there! We have deployed Active Directory Certificate Services on Windows 2008. There are still two more steps that must be completed. This is the process of restoring the Certificate Authority Database that was backed up in the first section and restoring the registry component.
To restore the registry simply locate the registry value that was saved above, right click the file and select merge. This will import the Registry settings to the W2K8 server. Next we have to restore the database. You can check to make sure the settings were imported correctly by going to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration and verify your settings are there. (Remember that screen shot?)
To restore the database and log files perform the following:
- Open Server Manager on the Windows 2008 Server.
- Expand Roles and then Expand Active Directory Certificate Services.
- Locate the name of the CA you just deployed.
- Right Click the CA name and select Restore CA…
- You will get a warning message that the AD CS cannot be running to perform this action. Simply click Ok to stop AD CS. AD CS will begin to stop
- On the Wizard click Next
- On the Items to Restore screen check the box Certificate database and certificate database log only. Click Browse to locate the database that was copied over above. (Note: I need to point out here that you select the folder you backed up to. i.e. if you backed up the database and logs to C:\Temp\CABackup then this will be the folder you will restore from. The backup process will create a subdirectory that it will look for during Restore, if you go one folder too deep the restore will fail.) Once you have located your backup click Next.
- On the completion screen click Finish and the restore will begin.
- Once the restore is complete you will receive a action box that asks if you would like to restart the AD CS. Simply click Yes. (We shouldn’t have any incremental backups since we are doing a migration.)
- Once the AD CS service is restarted we are good to go!
Well, what do you guys think? Worth the effort? Migrating to W2K8 AD CS will help your CA remain alive much longer. During this process I also had to renew the CA Certificate which was pretty much easy.
I hope this article will help someone out there, I know I was able to get through it but had to go to a couple of different sources to get the exact process down.
Enjoy!
Exchange 2007 and Journaling to a 3rd party (external) mailbox
by Scott on Feb.23, 2010, under Exchange Server, Microsoft Related
I recently performed an Exchange 2007 upgrade for a client who was moving from Exchange 2003. As part of their compliance with some regulations they are required to journal the activity of certain mailboxes within their organization. Journaling in this situation was enabled on the database level so all users in the database will have all emails sent and received forwarded to an external 3rd party mail server. This was done through a send connector to the 3rd party’s domain.
The problem the client was experiencing in Exchange 2007 was that all outbound emails originating internally were being sent to the external journaling provider however, all inbound emails were not being forwarded to the journaling provider.
The client contacted the Journaling provider and from a conversation it was determined that when an inbound message arrived to the Exchange Mailbox Server, it would be forwarded to the journaling provider from the original sender, the original sender being someone from outside the organization. This immediately put up a red flag in my head. I started to think, Exchange receives an email to send to a 3rd party, from a person outside of this trusted organization. Exchange was refusing to send the message! So, the thought came into play, how to configure this thing to allow it to relay to the 3rd party email server. Anyone? Anyone? Ok, the solution was actually quite simple and once I understood what was happening it was easy to figure out. I simply setup an Internal Relay! Yup, that’s it. The Internal Relay will allow Exchange 2007 to receive emails for a specific domain, query Active Directory for the mailbox and deliver the mail for that domain if it is found internally. If the mailbox is not found internally Exchange will then Relay the email for the 3rd party mailbox server specified in the Send connector which was already configured above! Walla, problem solved!
For more information on what an Internal Relay Domain is click here.
Have a great day!
Where’s My Single Instance Storage?
by Scott on Feb.22, 2010, under Exchange Server, Microsoft Related
The MS Exchange Team has a nice post (http://msexchangeteam.com/archive/2010/02/22/454051.aspx) on their site explaining the history of Single Instance Storage (SIS) and where it went!
Reading the article I couldn’t help think that many clients are still concerned about space on their SANs and fear the idea of placing anything on local disk. The idea in the article is placing your production mailboxes on Cheap Disk. The only time a client or anyone should consider this is where you are using Database Availability Groups and have at least three servers in the DAG. This will allow you to go backupless but also have all bases covered in your environment surrounding performance and recoverability.
My only other beef though is Archiving. The biggest question I get from clients is, “can I have my production mailboxes on one database and put the archived mail on cheap disk?” Currently in Exchange 2010 an archived mailbox is stored on the exact same database as the users’ production mailbox. I have heard rumors that this is being looked into for future releases but nothing concrete. What this means is that using SAN space which is typically RAID 10 or RAID 5 requires expensive disk for the production mailbox, which by default (if leveraged) archiving is also placed on expensive disk. Explaining to clients that they can use local disk, have HA, but need at least three mailbox servers isn’t easy. Not to mention that if you want multiple CAS in your environment with WNLB you need separate machines. This is due to WNLB and MS Clustering cannot run on the same server.
Otherwise, given the way Exchange is deployed these days it is an enterprise solution. There are times where departments will be included in a single database and other times where users are stored based on their last names. I do love what they have done with Exchange 2007 and then what they have also done with Exchange 2010. I just felt that I had to put in my 2 cents on the SIS discussion since I felt the post was a bit misleading. While the applications are true, we have to consider real life usage and still address client concerns.
Cisco Unity and Exchange 2007 on Windows 2008 R2
by Scott on Feb.19, 2010, under Exchange Server, Microsoft Related, Windows 2008 R2
So, an interesting call came to me last week regarding a client who was having some issues with Voicemails from Cisco Unity (I believe it was 7.0) transporting voice mails to Exchange. Their Exchange 2007 instance was moved from W2K8 to W2K8 R2 due to an issue they had with the W2K8 server. Not realizing that Unity (or Exchange) was not compatible with Windows 2008 R2 they started to have problems.
Basically the problem they were having was when a voice mail was left for a user, it was not being delivered to the user. Voicemails would pile up on the Unity server. The recommendation was to reinstall Exchange 2007 on a W2K8 server WITHOUT R2. The client decided to take a path to resolve the issue but I am not certain what they did.
On another note Exchange 2007 is not supported on Windows 2008 R2 yet, however I have heard rumors that if you install Exchange 2007 SP2 on Windows 2008 R2 if you run the install in Windows Vista Compatibility mode the install will work. When will Exchange 2007 officially support Windows 2008 R2? Well, Exchange 2007 SP3 will allow support for Windows 2008 R2. Exchange 2007 SP3 should be released some time this year (2010).
Moral of the story, do not put Exchange 2007 on W2K8 R2, and do not use Unity with Windows 2008 R2.
I also understand that Cisco Unity does not support Windows 2008 R2 domain controllers. Exchange 2007 SP2 will support Windows 2008 R2 domain controllers. So, take your pick, but you can’t use Unity to query W2K8 R2 DCs.
I hope this helps some people out there! Thanks for visiting.
My Client Visit Yesterday Part 2
by Scott on Feb.12, 2010, under Exchange Server, Microsoft Related
So, yesterday I was out at a client site to review their Exchange 2007 deployment. In my previous post I talked about how the Subnet the Exchange 2007 servers were in did not have the IP subnet associated with an AD site. Well, I did come across another interesting issue that was a bit more troublesome.
The client is deploying an Exchange 2007 SP2 environment leveraging a Single Copy Cluster (SCC) and two CAS/HUB servers.
While testing the failure over process of the SCC we came to the point where using the manage clustered mailbox command in the Exchange Management Console or the Exchange Management Shell would not work. We were receiving an error message that the Database failed to initialize. The error log was huge, errors on creating the D drive (where the database was located), errors opening the database, mounting the database, it just wasn’t working!
I then suggested to go back and use the MS Failover Cluster Management tool. We took a node off line, and failover worked. How Odd! This appeared to be an issue with permissions on the servers. Something was prevent Exchange from performing the failover. We then tried another failover vial the managed clustered mailbox command and I noticed that the shared disk drives were attempting to fail over to the passive node but they couldn’t!
We then proceeded to check permissions into the Windows Cluster and Exchange Cluster, adjusted a few settings but nothing worked. Well, I then asked, is there a Group Policy blocking any time of assignment to “Manage auditing and security log”, he said no. We checked Group Policy to be certain and there was nothing configured. I then asked him to take a look at the local security policy on the system, sure enough, only the Administrators were in the group Manage auditing and security log. Once adding the Exchange Servers to this group on each system the Single Copy Cluster was able to fail over with no problems!
I am not certain as to why the Exchange Servers did not get added to the local security policy, there was nothing in group policy or anything on the system to over write this to my knowledge. But none the less, it is very important to make sure the Exchange Servers do have access to the security setting.
Either way it was quite an interesting day at my client site, a few more issues came up but nothing as notable as the ones discussed here.
Hope you have a great day!
Microsoft Office Communicator 2007 R2 Group Policy Field Guide
by Scott on Feb.12, 2010, under Microsoft Related, Office Communicator 2007 R2
I was out looking around this morning when I came across this interesting gem: Microsoft Office Communicator 2007 R2 Group Policy Field Guide and thought, oh, do share!
The MOC 2007 R2 Group Policy Field Guide is a MS Word document that contains all the information an administrator wanted to know about MOC GPO settings but was afraid to ask.
This doc has everything an Admin will need. Here is a copy of the Appendix so you can see what options this document covers and is available for setting via Group Policy:
Appendix A. Policy Name Mapping Table
| Policy Name | Name in Group Policy Object Editor |
| AbsInsideURL | Address Book Server Inside URL |
| AbsOutsideURL | Address Book Server Outside URL |
| AbsUseFallback | Use in-band provisioning Address Book Server URIs |
| AllowUnencryptedFileTransfer | Allow transferring unencrypted files |
| AutoDiscoveryRetryInterval | Time interval to retry autodiscovery |
| BlockConversationFromFederatedContacts | Block conversation from federated contacts |
| CalendarStatePublicationInterval | Time interval to publish calendar data to presence |
| CallLogAutoArchivingPolicy | Enable/disable automatic archiving of call logs to Outlook mailbox |
| ConferenceAccess | Conference Access |
| ConfigurationMode | Specify transport and server |
| ConfiguredServerCheckValues | Additional server versions supported |
| CustomStateURL | Custom presence states URL |
| DefaultPersonalContactStore | Specify the personal contact store for PIM integration. |
| DGRefreshPeriod | Time Interval to Refresh the Membership of Each Distribution Group |
| DGUrlExternal (Replaces WebServiceURLDG) | Web Service External URL for Distribution Group Expansion |
| DGUrlInternal | Web Service Internal URL for Distribution Group Expansion |
| DisableApplicationSharingControl | Disables sharing control with users in an application sharing session |
| DisableAVConferencing | Disable Audio/Video Conferencing |
| DisableCalendarPresence | Disable Calendar Presence |
| DisableDataConferencing | Disable Data Conferencing |
| DisableEmailComparisonCheck | Disable email comparison check for Outlook PIM integration. |
| DisableEmoticons | Disable Emoticons in Instant Messages |
| DisableFederatedPromptDisplayName | Prevent showing the display name of federated, non-PIC, contacts in the notification dialog |
| DisableFileTransfer | Prevent file transfer |
| DisableFreeBusyInfo | Disable publishing free/busy info |
| DisableHandsetOnLockedMachine | Configure handset use on locked machine |
| DisableHTMLIM | Prevent HTML text in instant messages |
| DisableHttpConnect | Disable HTTP fallback for SIP connection |
| DisableICE | Disable Interactive Connectivity Establishment (ICE) |
| DisableInkIM | Prevent Ink in instant messages |
| DisableMeetingSubjectAndLocation | Disable publishing meeting subject and location information |
| DisableNTCredentials | Require logon credentials |
| DisableOneNote12Integration | Disable OneNote 12 integration |
| DisableOnlineContextualSearch | Disable online contextual search |
| DisablePC2PCVideo | Disable PC-to-PC Video |
| DisablePhonePresence | Disable Call Presence |
| DisablePICPromptDisplayName | Prevent showing the display name of PIC contacts in the notification dialog |
| DisablePresenceNote | Disable Presence Note |
| DisableRCCForwarding | Disable RCC Forwarding |
| DisableRTFIM | Prevent rich text in instant messages |
| DisableSavingIM | Prevent users from saving instant messages |
| DisableServerCheck | Disable server version check |
| DisableSimultaneousRinging | Disable simultaneous ringing |
| EnableAppearOffline | Enable the state Appear Offline |
| EnableConversationWindowTabs | Enable web browser in conversation window |
| EnableEventLogging | Turn on event logging for communicator |
| EnableFullScreenVideoPreviewDisabled | Enables Full Screen Video and video preview disabled for all OC video calls |
| EnableSIPHighSecurityMode | Configure SIP security mode |
| EnableSQMData | Specify instrumentation |
| EnableStrictDNSNaming | Enable strict DNS naming for server name |
| EnableTracing | Turn on tracing for communicator |
| EnableURL | Allow hyperlinks in instant messages |
| ExUMEnabled | Enable Voicemail Integration |
| HelpMenuText | Help Menu |
| HelpMenuURL | Help Menu |
| IMAutoArchivingPolicy | Enable/disable automatic archiving of IM conversations to Outlook mailbox |
| IMWarning | Warning Text |
| LocationProfile | Default Location Context for Phone |
| MapiPollInterval | Time interval to load calendar data from MAPI provider |
| MaxAudioVideoBitRate | Limit bandwidth for audio and video calls |
| MaximumNumberOfContacts | Maximum Allowed Number of Contacts |
| MRASServerURI | MRAS Server URI |
| msRTCLine | UC phone line information |
| NotificationsForNewSubscribers | Show notifications for new presence subscribers |
| PC2PCAVEncryption | Specify encryption for computer-to-computer audio and video calls |
| PC2PCASEncryption | Enables or disables application sharing encryption in peer to peer (2 user) connection scenarios |
| Portrange\Enabled | Specify dynamic port ranges |
| PreventRun | Prevent users from running Microsoft Office Communicator |
| PlayAbbrDialTone | Play abbreviated dial tone |
| Portrange\MaxMediaPort | |
| Portrange\MinMediaPort | |
| SavePassword | Allow storage of user passwords |
| ServerAddressExternal | |
| ServerAddressInternal | |
| SIPCompression | Configure SIP compression mode |
| TabURL | Tab URL |
| TelephonyMode | Telephony Mode |
| TourLaunchMode | Launch Microsoft Office Communicator Tour |
| TourURL | Optional URL for Microsoft Office Communicator Tour is a subvalue of Launch Microsoft Office Tour. See Launch Microsoft Office Communicator Tour. |
| Transport | Transport is a subvalue of Specify Transport and Server. See Specify Transport and Server. |
| VoicemailURI | Voicemail server URI |
| WebServicePollInterval | Time interval to load calendar data from web service provider |
| SafeTransfer | Attendant – Safe Transfer |
| MusicOnHoldDisabled | Attendant – Music On Hold Disabled |
| MusicOnHoldAudioFile | Attendant – Music On Hold Audio File |
| DisableBalloonWarning | Attendant – Disable Balloon Warning |
Also, if you’re looking for the Group Policy adm Template you can simply click here.
Enjoy!
My Client Visit Yesterday Part 1
by Scott on Feb.11, 2010, under Exchange Server, General, Microsoft Related
So, I was out at a client site yesterday to review the work they have completed so far on their Exchange 2007 deployment. There were two issues that we came across that were unique that I thought I would mention to the population out there. Hopefully this information will be able to help someone.
The first problem I noticed was the error message that stated Exchange was not part of an active directory site. This caused me to think, why would an error come up like this. My first instinct was to do a Gpresult /r (Windows 2008) which listed out all the information about the computer and user. The Computer said it belonged to the site Default-First-Site-Name. Ok, so the server was recognizing that it was a member of the AD Site, but why was exchange balking at the issue? Well, I asked the IT Admin to open up Active Directory Sites and Services and took a look in there. Looking over AD Sites and Services I noted the client had only one site configured, Default-First-Site-Name. Thinking a little bit more about the situation I asked to see what subnets were configured for the site. Well, upon review the site only had two subnets assigned to it. Neither one of these Subnets included the subnet Exchange 2007 was in. Talking to the Admin about this I learned that they had the same issue on the Hub Transport Servers and had to manually configure AD using ADSIEdit to insert the proper site name for the server to use! Eww, not sure how this will impact their environment in the long run but when installing Exchange this should all be done automatically. So, I had the admin add the Subnet to the AD Sites and Services and rebooted the mailbox servers, error gone, problem solved!
The moral of the story above? Make sure that you have your AD Sites and Services properly configured prior to deploying Exchange. Oh yea, don’t forget, you need to have a domain Controller in the same AD Site as Exchange. How the client ever got Exchange working is beyond me. The workstation was seeing the AD Site but Exchange was not, hence the error.
-
Howdy. Welcome to Scott Feltmann's Blog!
Thanks for dropping by! Feel free to join the discussion by leaving comments, and stay updated by subscribing to the RSS feed. See ya around!
-
Meta