KCotreau's questions

History: The history of this error, which has mostly gone unsolved, dates back to Windows 2000.

Platforms affected: Windows Server 2008 R2, Server 2008, Server 2003 R2, Server 2003, Server 2000 (both 32-bit and 64-bit installs are affected).

Error Messages

1. Event ID: 7024 The Routing and Remote Access service terminated with service-specific error 2 (0x2).
2. Event ID: 7024 The Routing and Remote Access service terminated with service-specific error 31 (0x1F).
3. Event ID: 7024 The Routing and Remote Access service terminated with service-specific error 20205 (0x4EED).
4. Event ID: 7024 The Routing and Remote Access service terminated with service-specific error 193 (0xC1).
5. Event ID: 20103 Unable to load C:\WINDOWS\System32\iprtrmgr.dll . (32-bit installs).
6. Event ID: 20103 Unable to load C:\WINDOWS\SysWOW64\iprtrmgr.dll . (64-bit installs).

You may have just seen my other question here.

One of the other things the client failed to tell me was that they also wanted a DAG between the U.S. and a site in Europe. I had never set up a DAG, but I did it, and opened a case with Microsoft to make sure I did it right. It seems fine, and everything replicates.

The problem is that when I attempted to test it failing over, it would not. I found information here that leads me to believe they may also need a hardware network load balancer, but I do not fully understand how it works, and how it makes Exchange understand that it has failed over. Could anyone explain that to me? I have looked.

Thank you.

I got thrown into a situation where I was asked to simply install Exchange 2010. The company has an IT staff, but they left out telling me that what they really wanted was to migrate a company from one e-mail system (POP3) to Exchange 2010, and they had already devised a plan to do it. They have about 150 users spread over a few locations.

Once I was well into it, it was clear that they had more in mind: Their intent is that they already bought a .net domain for Exchange that corresponds to their .com for POP3, and they intend to forward everything from the .com POP3 accounts to the .net Exchange accounts. They never really told me of this plan before I started, and as a sub-contractor, I was not even in on any of the preliminary discussions.

I am 100% sure that Exchange is working properly, and is in place. They are having problems with things like the reply from and other things related to the dual systems. I have my doubts these problems will be solvable, and that they should just make a fast move to Exchange and be done with it. The problem is that I doubt they will do this.

Since they are not far into the actual migration phase, are there any better ways to do this? Especially a better way to run them side-by-side, or should they just get everything prepared, and make one big move (which I am sure they will fight this idea)?

This week, we had an issue with Excel files opening slowly on the network. Some, despite being only 21K over 1000BT, took as much as 5 minutes to open. They opened fine locally.

Someone beat me to posting this on one of the sister sites, but since there are so many fellow system admins here, and I don't see it here also, I thought I would post the question and answer here too. I am sure I will save someone some time.

Of course, I realize the need to go to IPv6 out on the open Internet since we are running out of addresses, but I really don't understand why there is any need to use it on an internal network. I have done zero with IPv6, so I also wonder: Won't modern firewalls do NAT between internal IPv4 addresses, and external IPv6 addresses?

I was just wondering since I have seen so many people struggling with IPv6 questions here, and wonder why bother?

When you are remoted into a server that may be an hour away, and you have to reboot it, what is the best way to reboot it?

I am about to roll out Office 2007 to 1600 users. Most of it seems straight forward, but this client is particularly worried about macros and VB scripts not working. How do you migrate them in the first place? Does anyone have a good strategy on how to handle macros/VB scripts, which may currently be in use with Office 2003?

I am also hoping they will just work, but we may bring in a scripting expert just in case they need editing. If you know anything about lack of compatibility, I am also all ears.

Thank you.