SBS DHCP Server on a network with existing DHCP

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

dhoustonie

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Rant32: Sounds perfect! Exactly as i want and thought. Nice to point out changing the dhcp-options to the existing server. This is the answer.

dhoustonie
Thanks! The SBS is the new server who will replace the Standard server. I'm not really sure what we need to domains for, but we now have it - and may have use of it! So you tell us :-). We bought the old (Windows Standard 2003) server, on some stupid idea, with a single SATA-disc for two years ago. Of course we need to replace with a raid, before that disc will crash. We also need to buy Microsoft Exchange and Microsoft SQL Server. The cheapest way, and less disturbance, to do this was to buy a new SBS Premium as OEM together with new hardware.

I'm about to phasing in this new server in the network and attach the clients to it. Then disconnecting the old server, inserting a RAID, reinstalling it and make it an DC under the SBS domain. You have any ideas of how to split the functions of those servers? This is of course an another question..

Maybe consider using it as a Terminal Server? This is often a very useful function of a second server on a small network, if you have remote users who need access to applications.

If you have non-OEM Office cals (SA, OLP) then there's no need to buy extra licenses and this will make a great remote workplace.

Other ideas or stuff to off-load to this server:
- WSUS
- E-mail frontend
- Intranet webserver
- Print server

dhoustonie

When did you get the new sbs server? Was it after March 1st? If so you will be entitled to upgrade free of charge to the new version coming out of SBS called SBS 2003 R2, which will include WSUS and Sql 2005 Workgroup Edition.

As to movingg roles from the server, by dcpromo ing the server you will reduce some of the domain controller burden, and as Rant32 says you can move the Print server off of it to the backup server.

Again agreeing with Rant, by getting the terminal server cals you can give yourself the benefits of tight integration with the remote Web Workspace and give access to local resources to anyone that is offsite. Terminal server does not require raid or that level of redundency as all user files are saved to your existing server. Just becareful of licencing.

David

What you want to do is no problem... but first you need to change the domain on the old server to match the domain of your SBS.

Domain name change: http://www.microsoft.com/technet/downloads/winsrvr/domainrename.mspx

Adding SBS to existing Domain: http://support.microsoft.com/kb/884453

Jeff
TechSoEasy

ASKER

At this moment I run the new server as DHCP on the network, under difference domainnames. Everything seems to work perfectly, except that I can't reach a client through Remote Desktop from home (VPN), as I could before. And that the new servers domainname doesn't appear in the clients domainlist, but there no trust between those domain neither :-).

Rant32:
It's a nice idea! I also heard that SBS only have terminal server in administrative mode. Which not that good because application mode is what we need. WSUS also! Is there some way to failover SQL / access databases? If one server fails, the other server taking over? Is clustering the only way? Is there any possible benefits to make, regarding permission to files? I haven't use DFS yet but will look at it on this SBS. I think I missed something really nice there. I also think it's an nice idea to use the second server as licensing server.

dhoustonie:
Nice. Free upgrade, like those are impossible to recieve! I bought the server two weeks ago, so yes! It's after 1st march. At least if Dell doesn't bought the preinstalled licens before 1st march. When are this upgrade able? Is it now in days, weeks? Or as in some month?

My question of this thread is answered and I will soon close it, asking new questions later on :-)

<< I can't reach a client through Remote Desktop from home (VPN) >>
If you're using Windows 2003 Routing & Remote Access, either configure your old server as a DHCP relay agent, or set up the SBS box as VPN server. The new server's domain name doesn't appear in the list because of WINS issues, this is not related to trusts.

<< SBS only has terminal server in administrative mode >>
Yes, too many issues using a Domain Controller hosting IIS+Exchange+SQL+ISA server AND running user applications on top of that. You also shouldn't install Outlook on an Exchange server, so that's out of the question.

DFS is not really of any use with a single fileserver. DFS is used for consolidating file server resources so you have a single point-of-contact for all shares in the organization, and to make certain types of shares fault-tolerant by replicating data between fileservers.

Good luck.

<< Is there some way to failover SQL / access databases? If one server fails, the other server taking over? Is clustering the only way? >>

I believe Enterprise editions of SQL Server 2005 support database replication but I don't know if this can be used to make databases fault-tolerant. The only method I know of (that works, anyway) is clustering.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Rant32... one other point... DFS must be deployed on an SBS if Roaming Profiles are to be used... just FYI. See http://sbsurl.com/postinstall for more info on that.

Jeff
TechSoEasy

True, could use some clarification: By the front-end to Exchange, I meant the OWA web page so you don't have to publish IIS on the SBS and keep IIS for Intranet purposes.

With a limit of 75 clients, there is no need for a true FE/BE configuration.

<< DFS must be deployed on an SBS if Roaming Profiles are to be used >>

"Shares for storing roaming profiles and redirected folders could be added as links under a DFS root and the DFS paths could be used to configure roaming profiles and redirected folders. This simplifies the task of moving these folders later, if required.
[...]
Roaming Profiles should be used within a DFS namespace as described in the “Distributed File System” section in this chapter. This makes it easier to change the location of folders containing the Roaming Profiles, if required in the future."

Can you point me to the part where it says "must"? I can only find "could".

I don't consider this a technical requirement, and the advantage that the share name doesn't change when moving data to another fileserver is not specific to roaming profiles but applies to all data.

My apology... I overstated the point by using the word MUST instead of SHOULD. It's just a good idea, in my opinion.

On the point of running OWA on a different server, while it's possible, again not recommended because the Configure Email and Internet Connection Wizard creates and configures the OWA site automatically. Moving it would break the wizard which could cause other issues.

It is always my suggestion as well as that of many SBS Specialists that Small Business Server be installed using the default configuration to ensure that everything works... then, if modifications are needed, they can be done afterwards. This is certainly different than Enterprise settings where Network, AD and DNS planning is a major part of the deployment. Using the default config will significantly cut down on the long-term maintenance costs of an SBS... so usually it's better to spend a bit more on a beefier server than it is to try to spin off tasks that are part of SBS's feature set.

I would also point out to dingir that while both servers may be working on the network with two domains at the moment... the SBS will shut itself down 14 days after being introduced to a network which has another domain controller that holds FSMO roles and is a Global Catalog. So, this needs to be resolved ASAP.

You must add the workstations to the SBS's Domain and since you've not done a proper migration, you'll probably have to handle migrating the profiles by following the steps in this article:
http://www.certmag.com/articles/templates/cmag_howto.asp?articleid=819&zoneid=91

Jeff
TechSoEasy

P.S. These "musts" are NOT EXAGERATED.

ASKER

TechSoEasy
This question is answered is because it was about setting the new SBS servers DHCP on the network together with a windows 2003 server while configuring it. I've got that anser - I've disabled DHCP-server on the old domain and now running the DHCP-server on the new. That's works and thats why this question is answered! :-)

After that, the part of the old server - you are a second bit from agressive on that! :-). I will explain. When all clients are transferred to the new SBS-server (that's a new question i'm about to ask later) I just kill the old server, installing a RAID on it, reinstall the OS and thier clients and let it stand offline until I was given a nice way to use it. If there is possible to cluster this old server with the new - that's fine also! But still, that a third question :). Thanks very much for the upgrade to R2-information. That's comes a lot in hand.

Rant32
Thanks. I will came back with more specifik questions about this. WINS is nothing to care about at the moment. DFS is one question, because I thought that why I feel having no control over the network chares. I remember in Novell, I could select multiply specific maps to be visible as one virtual networkshare.

I'll be back. Thanks for very helpfull answers!
I need those very much later, when the server-exchange is going to begin :)

dhoustonie

R2 is still in beta and is expected to be released in the 2nd quarter but I would expect later on in the year, it would include wsus as a very integrated part of the server and server management tools.

David

dingir,

I'm sorry if you think I was agressive because I'm warning you that you only have 14 days from the time you added the SBS to your network to complete the migration of the workstations. Had you followed the domain rename on the old server you could have just added your SBS to the domain (per the KB article noted) without the need to migrate Active Directory User and Computer accounts... which now has to be done within the time constraints.

I think that warning you about this is quite reasonable.

Jeff
TechSoEasy

ASKER

Hi Jeff! Thank you! No it's ok.. of course :-). I'm just not interested in any migration of the workstations. Or do I don't know that much about it? I think it will be easier to manually copy every clients favorites, desktop and my documents (25 profiles) to new clean SBS-profiles. Because everything else will be difference or new. Drive letters, new GPO's, domains, usernames, roll-out of office instead of client-installed, routins for offline-files and so on.

I will came back for those questions later! Just keep the eyes up, there will be available points :)

Okay... no problem, just wanted to make sure you had the old server disconnected in time.

Jeff
TechSoEasy