Questions[windows-sbs-2003](server)

I'm working on a SBS2003 server, and I'm about to clean up on folder permissions. I notice that quite a few folders have the users SYSTEM and CREATOR OWNER set.

Now, I've found descriptions of the CREATOR OWNER user on the Internet, and I understand that this user is related to the creator of the folder/file. However, I'm unable to find any description of the SYSTEM user and what it is for. Can i safely remove it from folders/files? Will services running on the server suddenly not get access to those folders anymore?

We have a SBS 2003 installed in our office. Basically we have created 5 accounts, user1, user2, user3, user4 and user5 with coresponding exchange Exchange accounts.

Now we would like to have customized (client-friendly) Exchange accounts for different departments such as customerservice, accounting. What I have learned is that we could create distribution list which would actually take care of this problem.

But what about when we want to reply to our clients from lets say [email protected] instead of [email protected]? I think that would not be possible using the distribution list, so the only option is to create new accounts and mailboxes for customerservice, accounting etc.

So does it mean that we would have to create in this case 7 accounts and 7 exchange mailboxes? Would 5 licences be enough for this to work, or we need to purchase additional 2 licences so we dont reach any restrictions?

Thanks

I have a SBS 2003 server with Terminal Services enabled. Currently I am able to RDP to my server by going to www.mydomain.com. I would like to restrict RDP access to my network to be over VPN only. However, I am worried I will accidentally disable RDP to my server completely. How can I configure remote access to only be available when connected to a VPN?

On my SBS 2003 Server, I've been trying to access OMA unsuccessfully all day. When I first checked, the OMA mapping was missing, so I recreated the Vdirs per http://support.microsoft.com/kb/883380.

At this point, OMA was returning "A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator."

I then took the following steps, all to no avail.

I tried creating entries for the server's NetBIOS name on all of its IP addresses per http://support.microsoft.com/kb/898131

I tried adding an SMTPProxy entry per http://support.microsoft.com/kb/319681.

Someone mentioned that modifying the homeMTA information was incorrect and recommended updating it manually per http://support.microsoft.com/kb/319886

I also reinstalled ASP.NET 1.1, and when all else failed, I rebooted the server.

Attempts to access /OMA via the NetBIOS name, the FQDN, and localhost all generate Event ID 1503 (MSExchangeOMA) with a (501) Not Implemented error. Attempts to connect a mobile device (I've tried a WinMo phone and an iPhone) have generated Event ID 3005.

Any insight would be greatly appreciated.

Thanks

This case scenario started me wondering about the limitations of Small Business Server:

I have a client who came to us initially regading building them an intranet for managing staff training and document sharing etc. but as they use two other software packages (one for POS & one for inventory [they are not linked >< ]) I have advised them to start with looking at their overall I.T. infrastructure.

Bear in mind they don't have a dedicated I.T. staff member and their overall turnover I would guesstimate at a conservative AU $16M /year between 8 stores.

Infrastructure overview (as I understand it):

• One server ( I don't know the specs) hosted at main office running Small Business Server.
• Only one of the stores currently connecting via VPN to that server and the Inventory software running on it.
• Seven other existing stores to eventually connect to the server.
• Currently several hundred employees
• Company wants to double to sixteen stores within next 3 years.
• Probably ~20 (two/three per store) POS machines sending data to the server.
• Probably ~8-10 Desktop machines connecting to the server for Inventory/Backend

I found some links but would like to hear some real world experiences

http://www.microsoft.com/windowsserver2003/sbs/default.mspx
http://www.sbslinks.com/Us_v_them.htm
http://www.tomshardware.com/reviews/platform-small-business-server-2003,1151.html