Optimal iSCSI NIC Settings

Taken from http://austintovey.blogspot.com/2012/04/optimal-iscsi-nic-settings.html

Optimal iSCSI NIC settings

This can help eliminate TCP retransmits between EQL and the host.Find the 2x iSCSI NICs in the registry, only change this for NICs connecting to iSCSI storage.

Create two new DWORDS
TcpAckFrequency = 1
TcpDelAckTicks = 0

Restart the server.

The Microsoft Exchange Mailbox Transport Submission service terminated unexpectedly


Arrgg! My Exchange 2013 migration was going so well until I added a new receive connector to enable a secure relay for our copiers etc..I added another IP to the internal NIC to handle this duty.

I made the change Wednesday night and didn’t notice anything wrong until Thursday morning when people started calling asking what’s up with the email. I started troubleshooting with my analyst while driving the 30 minute trip and tried the usual suspects. Check the queues, building up. Reboot, no help. Finally check the event viewer and notice the MSExchangeSubmission.exe is crashing repeatedly. Stumped at this point so I undid the change made the night before.

Check the queues again and notice they are failing on a DNS failure. Huh? I have no problems with my DNS servers, why can’t it resolve DNS queries. Command prompt: ping google.com…100% success rate. ping …0% success rate.

Check DNS, the server is listed and has the correct IP address. Getting frustrated now. Modified the hosts file and added the server/ip combo in it and everything is magically better. A couple hours later with everything running smooth, I decided to add my receive connector IP address back onto the NIC. Head into a meeting and start getting calls again. Remove the IP and everything works again. Later that night, added the IP back and everything craps out. Long story short, this is a bug in Exchange 2013 somewhere that prevents it from detecting the NIC dns settings when you add a secondary IP to the NIC. Quick fix is to specify the DNS settings in Exchange (I used my internal dns for External DNS and Internal DNS) as viewed in the screenshot above.

Other than that, I migrated Public Folders today and shutdown my Exchange 2010 servers…so far so good.

Disable Acrobat Updates with a GPO


Finally Adobe and Microsoft are getting along with each other (kind of). With Acrobat XI, they have released a zip file with ADM and ADMX starter templates to control SOME features of Acrobat, one of them being updates.
They call these “starter” templates because they were too lazy to create the whole thing themselves. The good news is they do publish all the possible settings so you can easily modify the templates to suit your needs.

You can find everything here: Acrobat GPO Starter Templates

Good luck.

Exchange Server Edge Transport Reports Wrong Version


Excited to get started on our Exchange 2013 installs, we started with the mandatory schema extensions using: setup.exe /PrepareSchema
Oh CRAP! Not during the schema upgrade was my first thought. It failed because it said I needed to upgrade all my servers. I had run through all the requirements for co-existing an Exchange 2013 and 2010 environment including installing the Exchange 2010 SP3 update on every Exchange 2010 server role.
I start with my Edge Transport and run:

Get-ExchangeServer | fl name, admindisplayversion

Yep, it reports all servers at the SP3 level.
Next up is my Mailbox servers. Running the same command reports that my Edge Transport is still running SP2. What?
Long story short, you should/may need to recreate your Edge Subscription to get the version of your Edge Transport reported properly in the rest of the Exchange environment.
I used these commands:
Edge Transport

New-EdgeSubscription -File c:\edgesub.xml

Hub Transport

New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "c:\edgesub.xml" -Encoding Byte -ReadCount 0)) -Site "YOUR SITE" -CreateInternetSendConnector $false -CreateInboundSendConnector $false

Problem fixed…moving onto setup.exe /PrepareAD
Stay tuned!

Remove a DAG with Active Databases and other Exchange Tricks


More Summer Fun! We are preparing to install Exchange 2013 in our environment to replace our Exchange 2010. Our Exchange 2010 platform runs on our 3-node Hyper-V cluster with 5 virtual hosts and one physical as follows:
1 – Edge Server
2 – CAS Servers in an NLB Cluster
2 – Mailbox Servers in a DAG
1 – Unified Messaging Server (physical machine)

With the Exchange 2013 role redesign, I’ve decided to move to a HA configuration instead of CAS Arrays and DAGs. This will simplify management for my team. Our new platform will look like:
1 – Edge Server (Exchange 2010 Edge Transport because Microsoft wants you to move to their Cloud Services)
1 – Client Access Server
1 – Mailbox (Hosting 2 Mailbox Databases for staff)
1 – Mailbox (Hosting Archive Database and Unified Messaging)

Anyways, in preparation for the upgrade, I upgraded all the servers to Exchange 2010 SP3 and decided to nuke the failover capabilities before the upgrade to simplify things. Removing the CAS Array is a simple matter of removing the nodes and fixing a few DNS entries and mail routes.

Removing the DAG caused a little bit more anxiety as it affects our production databases and you have to click buttons that say Remove or Delete (my least favorite part of server administration).

Took a bit of Google work but I finally found a well written article to assist: Decommissioning Exchange 2010 DAG

I also had issues (doesn’t everyone) removing the Public Folder Replica. I don’t like having to resort to ADSIEdit but I’m pretty sure everyone thats ever tried to remove a legacy PF database has had to.

UAG SP3 Upgrade Process

While upgrading to UAG SP3, I missed the part where you should update TMG to SP2 Update Rollup 3. The UAG upgrade went smooth but didn’t work after I imported my old configuration. Luckily I had read enough to export the configuration which you need to convert to an SP3 schema using the UAGSchemaUpgradeUtil.exe in <UAG Install>\common\bin. After importing the config, UAG couldn’t update TMG properly with errors such as Firewall settings cannot be updated Error 0x80070057. I couldnt find anything online about it so let’s start troubleshooting.


Reinstall SP3….nope.

Hmm….upgrade schema and reimport the previous configuration….Ah HAH!

Apparently the schema update utility is dependent on TMG being at the proper SP level as well. Once I did this, I could also see all the firewall rules being created whereas before, there were only 4 rules.


Enjoy and this tip and RTFM!