Replies

Huh, weird. Here’s what’s missing:

DisplayName Company PrimarySmtpAddress Alias TotalItemSize(MB) Full Access Rights SendOnBehalf

Okay, I got past that problem by going into the unattend.xml file by using the GUI interface through the MDT (right-click the task sequence in MDT, left-click Properties, click the OS Info tab and click the Edit unattand.xml button).

In there I had to go into the specialize section, locate that IE Welcome Screen option, right-click it and select the option to revert the change (or whatever it said). Even if it says False already do this and it’ll fix the issue.

You actually can join a 2012 server to a 2003 funcational level forest/domain and Exchange 2013 will run in that functional level forest/domain as well.

Thanks. I think I’ll rebuild the 2012 box, join it to the SBS 2003 domain and then install Exchange 2013 and go from there.

But SBS doesn’t support domain trusts…

Thanks Paul. The problem with the whole thing is that the 2003 box has to remain up and the users have to be able to access it so they can continue using a single application that’s not ready to be used on the 2012 server. That’s the only reason why we can’t move everyone and everything off the old server and onto the new one. That was the original plan until my associate realized that the one application issue existed. So I have to have these two servers living side by side with the users being able to access the old application all day every day for a while. Using the 2 user terminal services license that the SBS box has by default (since it’s a server) isn’t an option. I’m just trying to come up with an easy way for the two servers to live side by side on the same domain. Any ideas because I was thinking the split DNS idea would work.

Interesting idea. The load balancer I was referring to is actually the RDS gateway, as it acts like a load balancer (sort of) and directs users to each of the two servers behind it based on server load. I do know that I tried creating a RemoteApp on rdsapp1 and rdsapp2 and in the setup I deselected the options to have it use a RD gateway server and the server name specified that it should connect to is rdsapp2, one of the servers behind the gateway. Unfortunately what I get is an error message stating that Remote Desktop Connection can’t connect to the remote computer. It states that the computer I’m trying to connect to, rdsapp2, is redirecting me to rdsapp1, and that I must use the farm name to connect.

Hi Paul. Thanks for the reply. I was just thinking the same thing about whether or not Exchange 2013 will run in a domain at the 2003 functional level. I think I have some digging to do… 8)

Hi Paul. Thanks for the reply. So what we were thinking might work is to join the 2012 server to the 2003 domain, add the AD and DNS roles to the 2012 box, also get Exchange 2013 up on the 2012 box (yes, we know you should have Exchange and AD/DNS on the same box), and move everything but the time and billing package to the new server and leave all of this up as long as is necessary. Once he’s able to put the time and billing package on the new server we transfer the fsmo roles and decommission the sbs 2003 box. The domain will still be a .local, but if we use split DNS it sounds like this could work. What do you think?

Okay, so from what I’ve read we should configure the internal and external URL’s to point to the external URL addresses – mail.company.com and autodiscover.company.com – and setup split brain DNS on the internal DNS server. So his DNS will have company.local as well as company.com. I’ve looked at the information at the following link – http://www.petenetlive.com/KB/Article/0000830.htm – and am wondering if this is all I need to do in order to setup split brain DNS so it will work with my friend’s situation?

Thanks for the information Paul.

Thanks for all the help everyone. One last question…

I’m sure there’s a big speed difference between an LTO 3 or 4 tape backup system and a RDX USB 3.0 backup system. However, there seems to be about a $1,000 price difference when you add in everything (backup hardware, cartridges or tapes, and add-on cards). For a small business with 1 server and 10 users do you feel like a RDX USB 3.0 backup system would be at least an okay idea if not a good idea?

Here’s the make/model of the one from Newegg he’s looking at. It’s a SAS connected device so I guess he just purchases a SAS add-on card to go with it?

http://www.newegg.com/Product/Product.aspx?Item=N82E16840119042

Thanks for the info. I’m a little confused about the Bluetooth stuff. Take this item for example:

http://www.magic-pro.com/en/product/other/ProMiniBTTouch2.htm

It looks pretty cool, but what confuses me is that the system requirements include a Bluetooth enabled PC (if you want to use it with a PC). However it shows that it comes with a Bluetooth dongle. I don’t get it. I thought the Bluetooth dongle is what you’d plug into your PC but now I’m wondering if the Bluetooth dongle plugs into the keyboard/mouse device to provide it with Bluetooth, and thus you’d need a Bluetooth enabled PC.

Am I right? Does that make sense?

Good to know. Actually, so now the question is whether or not to use Bluetooth vs. regular 2.4 GHz RF. Which is better? The keyboard/mouse unit won’t every be used more than 15′ away from the PC. Any thoughts?