Answer by Richard
The underlying operating system is the same between the two. Its windows 2003, the difference is that additional applications that come bundled with the Small Business Edition.

Ideally in a larger company windows server is installed on one machine and runs one application using seperate servers for email, database and proxy services. Since small businesses usually can’t afford many different hardware and software systems SBS comes with several useful applications and is designed to be installed just one machine. There are two versions of SBS the premium version has Exchange(Email), SQL (Database) and ISA (Proxy/firewall) server.

http://www.microsoft.com/windowsserver2003/sbs/evaluation/features/default.mspx

The Standard SBS edition only comes with Exchange. The other services you see on the microsoft site also come included in plain windows server 2003 however microsoft includes some installation scrips with SBS to make the insall process easier.

It’s microsoft’s attempt to get in on the small business market with applications that are often used by some of the biggest enterprises. You save money over buying the applications individually however the limitations are you can only use one physical computer. You have to buy a transition license to “split” the component applications onto multiple machines once your business and needs expand.

SBS is a good deal if you can only afford one server and are prepared to put all your eggs in one basket. If your server goes down so does everything. If you have a lot of users you may also need to higher end hardware, this is when sometimes many low cost servers could meet your needs better than one single high end server.

Give your answer to this question below!

Best answer:

Answer by worldneverchanges
Create a folder to be shared by all users. Download the update into that folder. You may have to download the exe version. On the client computers change the update setting to point to the folder and file. You should be able to schedule it to run on the client computers.

Know better? Leave your own answer in the comments!

Best answer:

Answer by Developer
Yes, you can install it

Give your answer to this question below!

Best answer:

Answer by ratter_of_the_shire
be careful. Run a linux liveCD, and look at the output of “lshw -short” to identify all the system components. Then verify that each of the vital ones have drivers availible for server 2003.

For all you’ve told me it may not even be an x86 processor. (could be itanium, sparc, or PPC) so you may want to examine the board a bit to get a better ID on it.

If so just boot from the windows install disk and follow the step by step.

also 32 v 64 bit is dedicated soley on the hardware of the sever box. Go 32 bit, unless it has both more than 4GB or RAM and a 64-bit compatible processor.

Give your answer to this question below!

drive:\Setup\I386\Setup.exe /DisasterRecovery

See Recovering a failed Exchange 2003 server:

http://www.msexchange.org/tutorials/Recovering-Failed-Exchange-2003-Member-Server-Using-Disaster-Recovery-Switch.html

The relay restrictions are stored under a series of REG_DWORD and REG_MULTI_SZ values under the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\MSExchangeIMC\Parameters

For more information please see the following Microsoft KB article:

http://support.microsoft.com/kb/193922

Check it out:Clint Boessen’s Blog

I have all of the information needed to enter at any of the prompts, but I don’t know the process. I helped when the computers were first put in, but I neglected to write the process down.

The workstation will be a WIN XP Pro

You can email me if you like with any other questions.

The following is information on the server:

Dell Power Edge 1900, 4 Gig RAM, duel quad core
MS Server 2003 Standard
File, print, WINS and Application server = Default Settings
DNS server = yes
DHCP = yes
terminal services and remote desktop = no
Okay, I’ll need help with assigning the IP address to the computer, each one has its own, they aren’t generated randomly. We definately did something with IPCONFIG at the DOS prompt.

Best answer:

Answer by azcn2503
You’ll need to open the Properties of My Computer (System Information, sysdm.cpl), then go to the Computer Name tab, and change the Computer Name to fall in line with the naming convention you use. You’ll need to change the Workgroup option to Domain, and type in the Domain name (probably yourdomain.com or yourdomain.co.uk) then provide an administrative username and password on that domain in order to join. By clicking OK, and OK again, restart the computer, and you should be greeted by the Ctrl+Alt+Del screen or whatever screen your Group Policy specifies.

Give your answer to this question below!

Best answer:

Answer by Andy24
no clue

What do you think? Answer below!

Best answer:

Answer by sgtjnlawrence
Sounds like you would like to push software out via group policy to these computers. You would need to make your Windows 2003 server a Domain Controller first. Then add all your PC’s to that domain. Then you can push software to the computers via a Software GPO. You can get more info on deploying apps at www.appdeploy.com

Add your own answer in the comments!

Best answer:

Answer by Sly_Old_Mole
The virus I don’t know; however the fact that it uses USB must mean that it uses autorun.inf.

http://experi3nc3.wordpress.com/2007/05/10/flash-disinfector-by-subs/

Know better? Leave your own answer in the comments!

An error occur ed while trying to establish a connection to the Exchange server. Be sure that port 443 (for SSL) or port 80 (for non-SSL) can be reached. If you are connecting to public folders, be sure that the public folder store is mounted. If you are connecting to mailboxes and the progress bar shows a particular mailbox, be sure that user has at least one email address.

Exception: Failed to connect using secure URL: https://domain.local/ExAdmin/Admin/domain.local/public%20folders/ with error: The underlying connection was closed: Unable to connect to the remote server.. Failed to connect using unsecure URL http://domain.local/ExAdmin/Admin/domain.local/public%20folders/ with error: The remote server returned an error: (503) Server Unavailable.

This error gets generated if you have a proxy server configured in Internet Options. What caught me out however is PFDavAdmin only detects proxy settings on application lauch… not on connection. If you remove your proxy settings from Internet Options, then attempt to connect again using PFDavAdmin the same error will be reproduced as PFDavAdmin will continue trying to use your proxy settings.

You must:

1. Disable your proxy server or add an exclusion.
2. Close PFDavAdmin
3. Relaunch the PFDavAdmin application.

Check it out:Clint Boessen’s Blog