Re: SBS Server or Windows Server?
Tech-Archive recommends: Speed Up your PC by fixing your registry
Marci,
Prior to doing Allen's recommended step 1, make sure you have the
administrator password to the server. Then in rapid succession, change the
admin password and any other passwords he may know, FIRE YOUR IdioT GUY, and
find another one to administer your network. There are plenty of competent
SBS folks out here!
Gregg Hill
"Marci" <Marci@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:939E5F1B-5E43-4F97-A543-24CB0B912631@xxxxxxxxxxxxxxxx
> Allen,
> Funny you should mention that. I just requested from my IT that he give me
> specific reasons for 1) purchasing a new server and 2) eliminating SBS.
> His
> reasons were exactly what you just stated. He said my current server has
> "no
> redundancy", and that I am "running too many services on one server." The
> thing is, I DO have another server that he just charged me to set up two
> months ago. I thought THAT was supposed to run the services or
> applications.
> It runs Windows Server 2000. He aslo is now warning me that I do not have
> an
> option. My server will fail and I will have no network functionality at
> all.
> I do have an external hard drive that I had assumed was performing
> backups.
> This whole thing is driving me nuts. I just want to do something simple -
> like tax returns.
>
> "AllenM" wrote:
>
>> Hi Marci,
>> Well Im sure by now form all the responses you are getting it may be
>> getting
>> a bit confusing here for you. So let me break down what the consensus is
>> from the responses you have received.
>>
>> 1. Fire the IT guy. A majority consensus.
>> 2. If there is a hardware issue with your current server (i.e.
>> motherboard)
>> you do not have to get another server and switch to Windows 2003 Server.
>> Depending on how old your server is you may still be under warranty to
>> have
>> your issues resolved at no expense. If not get a person who is hardware
>> knowledge to do the work
>> 3. You are a perfect shop to be using SBS 2003. Stay with it and hire a
>> consultant who is SBS "savvy".
>> 4. The only reason you would have a need for another server (Windows 2003
>> server) in your existing SBS domain would be as an application server or
>> file server. You will not have to purchase any extra CAL's. If you buy
>> another server with Windows 2003 Server it will be legally licensed to
>> use
>> in your SBS network. You do not want to be running applications on your
>> SBS
>> server so you may want to consider this seeing how you run several
>> applications and store large amounts of data.
>> 5. Being a small shop it is not economically feasable for you to buy
>> another
>> server just for redundancy. A smart IT guy would know how to apply a RAID
>> fault tolerance for your existing server. I would suggest you have some
>> type
>> of tape backup or perhaps another external device to do your backups.
>>
>> Hope all this helps.
>>
>>
>>
>> "Marci" <Marci@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:FD035A23-FD99-4388-921E-A30E7B612A83@xxxxxxxxxxxxxxxx
>> > You folks have been excellent at explaining these things to me. Allen,
>> > you
>> > ask what "specifically" is wrong? I'm going to paste his response to me
>> > here
>> > and maybe you can understand it. I can't. He says, "Bottom line is that
>> > you
>> > need to get another box on your network. Both scenario's (SBS or
>> > Server
>> > 2003) do not require us to rebuild you network; therefore saving time
>> > and
>> > money. You need redundancy no matter how you look at it. Even if you
>> > decide
>> > to to keep SBS 2003, you still need Windows Server 2003 Software
>> > Licenses
>> > for
>> > your remaining servers. Why not just implement Server 2003; take
>> > advantage
>> > of it's ability, and have a much more redundant network. In my
>> > opinion, I
>> > would not recommend keeping SBS because you have to many things wrong
>> > with
>> > your current SBS Server to do the migration."
>> > I'm not sure what is currently wrong with my SBS Server. Does this mean
>> > anything to you folks?
>> > Marci
>> >
>> >
>> > "AllenM" wrote:
>> >
>> >> I forgot to ask that you check with your IT guy and ask him to be a
>> >> bit
>> >> more
>> >> "specific" on what the issues are that leads him to think your server
>> >> is
>> >> dying. sounds very generic to me and I'm sure you will get a lot of
>> >> the
>> >> Newsgroup people to agree that this IT guy has no clue to SBS and his
>> >> suggestion to downgrade and switch you over to Windows 2003 Server is
>> >> simply
>> >> because he is familiar and comfortable with working in that
>> >> environment.
>> >> Ask
>> >> him if he is going to load Exchange, ISA and SQL server on this new
>> >> Windows
>> >> 2003 Server and if it will also be your print server. file server and
>> >> where
>> >> is he going to put your company web at? If he says he will install
>> >> them
>> >> all
>> >> on the new server, fire him immediately.
>> >>
>> >> "Marci" <Marci@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:79400F86-0F66-467B-9652-E1CC7D460ED9@xxxxxxxxxxxxxxxx
>> >> >I am not an IT, but didn't know where else to go for answers... A
>> >> >year
>> >> >ago
>> >> >I
>> >> > purchased Windows Small Business Server 2003. I own a financial
>> >> > services
>> >> > company, have a 10 computer network, run multiple applications and
>> >> > store
>> >> > large amounts of data. (We are currently converting stored docs to
>> >> > electronic.) Recently we've been experiencing some issues that,
>> >> > according
>> >> > to
>> >> > my IT (outside vendor, not an employee), indicate that my server is
>> >> > dying.
>> >> > He
>> >> > is now informing me that we need to move to Windows Server, and to
>> >> > eliminate
>> >> > Windows Small Business Server. He says that SBS does not permit
>> >> > another
>> >> > server to be present (something about domain control), and that the
>> >> > entire
>> >> > process for moving to a new network will take approximately 80
>> >> > hours,
>> >> > as
>> >> > you
>> >> > can't move from SBS direct to Windows Server. He says that simply
>> >> > purchasing
>> >> > a larger server will not fix the problem. We also use Exchange -
>> >> > heavily.
>> >> > He
>> >> > says that this might be a problem, as we will lose all but our basic
>> >> > Outlook
>> >> > contacts. We have customized Outlook with multiple forms, etc.
>> >> > Gosh -
>> >> > am I
>> >> > about to lose everything? What is the best route to go? I'd
>> >> > appreciate
>> >> > any
>> >> > responses.
>> >>
>> >>
>> >>
>>
>>
>>
.
Relevant Pages
- RE: Service Pack 1 on SBS 2003 Premium
... reinstalled the SP1 from CD again, ... Restart Windows Management Instrumentation service. ... Close the registry editor and restart the server at a non-business time ... Have you applied the whole SBS SP1 successfully? ...
(microsoft.public.windows.server.sbs) - RE: Service Pack 1 on SBS 2003 Premium
... reinstalled the SP1 from CD again, ... Restart Windows Management Instrumentation service. ... Close the registry editor and restart the server at a non-business time ... Have you applied the whole SBS SP1 successfully? ...
(microsoft.public.windows.server.sbs) - Re: The list of servers for this workgroup is not currently availi
... Select Windows Small Business Server 2003 and then click Change/Remove. ... You may prompt to inset SBS installation CD. ... Our only problem w/ connecting to the branch office is mapping ...
(microsoft.public.windows.server.sbs) - RE: SBS 2003 Standard - Update to SP 1 fails
... order to prepare SBS server to deploy Windows XP SP2 to client computers ... that are running Windows XP Professional. ... The SBS SP1 launcher need copy ... please install it and then ...
(microsoft.public.windows.server.sbs) - RE: Service Pack 1 on SBS 2003 Premium
... You can monitor your server for some time to the Companyweb ... This newsgroup only focuses on SBS technical issues. ... >reinstalled the SP1 from CD again, ... Stop Windows Management ...
(microsoft.public.windows.server.sbs) |
|
