Chris
Mon May 08 15:46:01 CDT 2006
More food for thought. I thought the TS issue you write about below was what
I had read as well. I was also wondering why the person that set this whole
thing up set it up on one box. I'm in near manchester NH in the USA. Can I
breat out TS from my SB server 2000 and run that on a green box and then just
migrate my current server to a better box?
Chris
"SuperGumby [SBS MVP]" wrote:
> and Chris, please note, it is highly desirable that a TS Application Mode
> server IS NOT a DC. Be aware that Microsoft have blocked the ability to run
> SBS 2003 as an application mode TS. If you wish to use Terminal Services in
> an SBS2003 domain you _must_ have an additional server, TS2000 or 2003 are
> fine.
>
> I agree with Merv's advice but if you are 'the desktop guy' it may be
> beneficial to mention where you are, a migration to SBS2003 on the new box
> would be strongly recommended, but even though Jeff's www.sbsmigration.com
> Swing IT!! process is extremely well documented and supported it is not a
> job for someone new to this sort of thing. Maybe we have someone familiar
> with the process near you.
>
> "Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in message
> news:%23v9VyqtcGHA.1272@TK2MSFTNGP03.phx.gbl...
> > When you say that the SBS 2000 is running Terminal Server, do you mean
> > that it's running Terminal Services in Application Mode? i.e., users TS
> > into your SBS 2000 and remote control the server? Or are you just doing
> > administrative tasks on the SBS 2000 via Terminal Services (in Remote
> > Administration Mode)?
> >
> > SBS 2000 or 2003 require that all components (Exchange, ISA, SQl, etc.)
> > stay on the SBS server. So, the SQL 2000 that you now have must remain on
> > the SBS 2000 server. Same would be true with SBS 2003 (Premium). The
> > cost of buying SQL 2000 + CALs to put on a new server may be excessive.
> >
> > Again, how many users are we talking about who need access to the SQL
> > proprietary software package and how many users need to TS into the
> > domain?
> >
> > The only reason I mentioned migrating SBS from the old server to the new,
> > is to maintain your Active Directory settings for users and permissions on
> > all the shared stuff. If you don't have more than a handful of users, you
> > "could" do a fresh install of SBS 2003 on the new hardware, Exmerge the
> > Exchange accounts to the new SBS 2003 server (or just copy them to a .pst
> > and import them into Exchange 2003). Then you could copy over all user
> > data and other databases from your apps to the SBS 2003 server, recreate
> > the user accounts and share out the data folders. However, this approach
> > would also require you to recreate new profiles for each user(s) on the
> > workstations. That's the beauty of the SwingIT approach at
> > www.sbsmigration.com... the workstations don't have to be touched. As far
> > as they're concerned, nothing has changed with the SBS server, even though
> > you've installed a new one and upgraded to SBS 2003.
> >
> > --
> > Merv Porter [SBS MVP]
> > ===================================
> > "Chris" <Chris@discussions.microsoft.com> wrote in message
> > news:9586FD3C-A2E1-44D8-BBF8-BAD628825B46@microsoft.com...
> >> Let me look this over and see if I understand it. At first glance it
> >> seems
> >> pretty tough and well over my head as the adv. desktop gotcha guy for the
> >> company.
> >>
> >> Chris
> >>
> >>
> >> "Merv Porter [SBS-MVP]" wrote:
> >>
> >>> Just a thought...
> >>>
> >>> How many domain users and TS users?
> >>>
> >>> What about upgrading to SBS 2003 on the new hardware by purchasing the
> >>> SBS
> >>> 2003 version upgrade and Version Upgrade (VUP) CALs and migrating SBS
> >>> 2000
> >>> to the new hardware? Then run the proprietary software app on the SBS
> >>> 2003
> >>> server. You'll have SQL 2000 on the SBS 2003 server. If you purchase
> >>> another server to run the Proprietary software, you'll need to
> >>> separately
> >>> purchase SQL 2000 + SQL CALs.
> >>>
> >>> Then take your present server, buy Windows 2003, invoke your downgrade
> >>> rights, install Windows 2000 server on it as a member server (as long as
> >>> you
> >>> can find the Win2K server media from MS Worldwide Fullfillment) then set
> >>> up
> >>> the member server as a TS2000. SBS 2003 will cover access to any member
> >>> server in the domain, so all you need is a Win2K3 server license for it.
> >>> All your Win2K and WinXP Pro workstations accessing the TS2000 server
> >>> will
> >>> get a "free" TS CAL from the TS2000 pool.
> >>>
> >>> If you install Win2003 as a TS2003 server, you'll need TS CALs for each
> >>> user/device accessing the TS2003 server. Of course, this assumes that
> >>> you
> >>> don't want/need any of the feature improvements associated with TS2003
> >>> (which I believe aren't many).
> >>>
> >>> Migrating SBS 2000 to SBS 2003 on new hardware
> >>> www.sbsmigration.com
> >>>
> >>> Pricing for SBS 2003
> >>>
http://www.microsoft.com/windowsserver2003/sbs/howtobuy/pricing.mspx
> >>>
> >>> This setup would require only 2 boxes (one new, one existing) and you
> >>> get
> >>> SBS 2003 and all it's upgraded feature set - well worth the money.
> >>>
> >>> --
> >>> Merv Porter [SBS MVP]
> >>> ===================================
> >>> "Chris" <Chris@discussions.microsoft.com> wrote in message
> >>> news:A35E0D02-D8CD-4983-ACAC-23F134D7E556@microsoft.com...
> >>> > Hello: I currently have a single server office running SB Server
> >>> > 2000.
> >>> > On
> >>> > that server I'm running terminal server as well as exchange server.
> >>> > The
> >>> > server itself is a dell 1400sc, PIII 1.4 gig CPU. Our proprietary
> >>> > software
> >>> > supplier has talked us into an upgrade of their software and the
> >>> > current
> >>> > server will just barely cut the specs plus I have to run sql server
> >>> > for
> >>> > the
> >>> > new upgrade of the software. So I'd like to post my idea how to deal
> >>> > with
> >>> > this and get some feedback from this great group.
> >>> >
> >>> > First I would keep my current SBServer 2000 acting as the DC and
> >>> > running
> >>> > exchange. From what I've read Exchange must be on the DC? I would
> >>> > buy a
> >>> > new
> >>> > server with server 2003 and set that up to run the program we are
> >>> > upgrading
> >>> > along with sql server. Finally I thought I'd take a green box and use
> >>> > it
> >>> > for
> >>> > terminal server.
> >>> >
> >>> > I'm not sure if I can do this last step. I think I've read the TS
> >>> > must
> >>> > remain on the DC so help here would be much appreciated. I think/hope
> >>> > I've
> >>> > written things out clearly.
> >>> >
> >>> > My reason for adding a new server and keeping the old is to make the
> >>> > change
> >>> > over easy. I think the toughest part would be setting up a new DC and
> >>> > doing
> >>> > all the transfers such as exchange and AD.
> >>> >
> >>> > Well thank you in advance. Chris
> >>>
> >>>
> >>>
> >
> >
>
>
>