Window Server 2003 Small Business in Mexico

[TullyMars]

New Windows person here. (Mostly a Mac guy.. sorry)
We are looking at opening a remote office in Tijuana Mexico. I want to put a Server in place down there that we can access from San Diego, Colorado, etc.

But... I am being told that if I buy MS Server 2003 ... any version ... in the US, I can not use it in Mexico?

I am talking about buying the software with all the appropriate CALs.

What are my issues to put this item in Mexico?

Thanks...
Tully Mars

 

[ShackDaddy]

I think if it is purchased, configured and owned by a US company, there aren't any laws about where it will be used. I'd just go ahead.

Dave Shackelford
Shackelford Consulting

 

[goombawaho]

I had this experience trying to buy servers for 3 Mexican offices from IBM. They would not sell it to me (in the U.S.) with the idea that it would go to Mexico because they would not support it.

But it's not a good idea in general even if you told them it was for the U.S. and shipped it to Mexico. You need to have it purchased in Mexico for warranty and tech support. Tech support always asked where the server was (at least IBM
did).

And they get real fussy about shipping stuff in. I wouldn't risk the customs hassle - they often damaged products as they opened them up to check out "country of origin" on many items. Better to buy within Mexico from an authorized distributor of your brand and then no destruction at the hands of customs. I'm not kidding, they would open up the PC case and pull out video cards to check for country of origin.

 

[ShackDaddy]

Good call, but if the main office is in San Diego, chances are they'd just be driving it over to the TJ office themselves 45 min away, so there wouldn't be quite the same issues with shipping. I've never had a vendor ask where a server was for support services, but I've rarely worked with IBM either.

Dave Shackelford
Shackelford Consulting

 

[TullyMars]

Thanks Folks.
I assume that every time a remote user logs on to the server, that Microsoft verifies the validity of the Client Access License. Right? And therefore would be able to determine the location of the actual server?

I am not too worried about support of the system. We have access to very good and cheap guy in Mexico to set it up, administer, maintain...

I just don't want Microsoft to "invalidate" the licenses because of the location.

 

[goombawaho]

Don't take the chance. You could get in trouble at the border if they decide to thoroughly inspect your car and see the server. Strip search anyone???

Just don't fool around with it. But do what you want - roll them dice. Go ahead, be my pest.

 

[TullyMars]

Thanks Goomba....

But I am not worried about the Mexicans. I cross the border 4 or 5 times per week. No biggie. If they stop me... (about a 1 in 20 chance), the most I will need to do is pay the import fee of 10%. Show them the receipt and pay the dough. 1000 dollar server... no big deal. But a 20 Spot would handle it as well.

What I am worried about is Microsofts' licensing issues when they can see the location of the server and therefore the software? Do they care? Does the license prohibit use outside of the good ole USA?

Thank again...
Mars

 

[ShackDaddy]

Tully, I've never heard of such a thing, and I doubt that M$ checks the originating IP network of a WUS connection for that purpose. Also, M$ doesn't communicate with the server every time a remote user connects. M$ communicates with the server once, when you first install the licenses, and that's it. All further license verification is done by the server when it looks at its own local license count. There is no further license-related communication with M$.

Dave Shackelford
Shackelford Consulting

 

[TullyMars]

Thanks all..
I think I understand.

Tully