Re: Cannot activate SBS 2003 SP2


Davo, mate..more the merrier -

Are you a clarevioant? Do you have a backdoor link to my PC? How did u know
that in the study that my missus used to keep like a surgery are cd's, power
supplies, routers, cases, motherboard boxes, keyboards, wires snaking
everywhere and sitting on the case of the server is the old board - balanced
on a MB static bag and a plastic folder?

So yes thats what I have done - Reinstalled the poxy 2003 software all the
way through to the bitter end on the old board and once all is hunkey dorey I
will drive the system disk into the heart of darkness that is the new MB -
That will be entertaining - I love a good scrap

Thank goodness for the advice from david, sue and yourself on the correct
sequence for installing all the many iterations of the software that exists -
I get the feeling though that MS have created a monster that is hard to deal
with.

BTW havent used the adaptec array card yet - just have one system disk at
the moment - about to clone the system disk - bloody hell - wish I did that
the other day - and then try the raid card.

the old array was a raid 5 (4 disks) that should not have become so rooted
but the twit who built the server did not actually enable the spare drive to
act as a spare!!

Anyway - just about to crank up the new MB - its all shiny and new with red
bits and spikey bits all over sort of alien looking - unlike the original
that looks like a soviet era kitchen - It MUST be a ripper if all the shiny
bits are actually not just for show...

Thanks again - will keep all you darlings posted - will give u something to
look forward to what!

Len

ps Dave if you are pom then you gonna get yo ashes ass whipped by us...


Not meaning to intrude on this glorious thread...
But got a 'silly' suggestion, that has worked on w2k, xp & even SBS before..
Put the OLD mobo in..
Build the system fully, service pack, service pack hotfixes etc...
Swap the mobo..
as the system is booting off the adaptec raid card, it should still boot but
go potty about missing drivers etc..
faff about and add in the required drivers...

judicious imaging along the way will aid the numerous retries needed..

BTW dont forget to set the DNS ReservedPort registry entry (see
http://bitsolve.spaces.live.com/blog/cns!D0597DCC1B3A70EF!288.entry)

David Barnes


"Susan Bradley" <sbradcpa@xxxxxxxxxxx> wrote in message
news:#9tCo84$JHA.5040@xxxxxxxxxxxxxxxxxxxxxxx
Which OEM manufacturer? As some do allow you to order replacement media?

Len Turner wrote:
was an oem - but MS agreed that I could replace the MB - arent they
sweet - cannot get "slip" media from MS so i guess the previous praise is
relative - "Susan Bradley" wrote:

SBS is not Windows 2003 plain is the problem and if it was this easy to
slip stream SBS you would have had it ages ago. The problem is SBS is
unique and I've rarely if ever seen it work.

How did they buy this Server? OEM or retail?



Len Turner wrote:
Sue, No need to apologise - a bit of stirring makes the day go by..

No I dont know anyone else who has 2003 sp1slip disk - and again
pardon my ignorance of the SBS vernacular - what exactly is a "slip
disk" - is it the later release of the server 2003 software? and as you
have not hammered me over my question about combinig server 2003 sp0
and 2003 sp1 - does that create a "slip disk" or not - consider it a
continuation of my education into the arcane worls of MS Server stuff.

As far as I can tell MS advise that slipstreamung is kosher - why are
you so dead set against it - is it ok in principle and gets stuffed up
in the process? or is it never an option.
Another drama was that disk one of the original 2003 server was
scuffed by a dodgy cd drive so i had to get it polished out at the
local video store - seemed to work ok then but it may be a factor.

And when you say "their keycode" do you mean the keycode that comes
with the other persons SP1 or SP2?

Thnks again

"Susan Bradley" wrote:

Again I apologize but I'm tired of seeing too many people screw up
trying to make this slip media.

On the bsod, do you know which driver is the offending one?

Next do you have any other customer with SBS 2003 sp1 (or sp2) slip
media that you can substitute but use their keycode?

Len Turner wrote:
Ok Sue - Thanks for your dagger slipped into the ribs albeit held in
a velvet glove.. but you are correct really - I need to get a grip

This is network server for a friends business who has zero budget.
and i mean ZERO.

The server has been chugging away in a small business environment for
several years and I have administered it for them for about a year
making sure that the updates were installed and their mailboxes were
managed etc etc.
I left them a few months ago and the server was administered by
another fellow who ignored some critical warnings and was annoyed at
the shrill alarm coming from the Adaptec RAID card warning of a
degraded array so the system disk crapped itself and the array could
not recover. (cause the original setup
So I decided to rebuild the server from scratch using new components.
My main reason for slipstreaming the install is because I cannot get
the original 2003 server install to cope with the new hardware and it
falls over part way into the install - BSOD bit.

The slipstreamed sp1 install however completes the process so i
figure an update in the SP1 was able to cope with whatever the
original 2003 server CD couldnt.

In reading other blogs here it seems that there are several staged
updates that need to be applied if one is to have a succesful outcome

So here is my dilemma - I cannot get past the first post cause i need
whatever update is on SP1 to cope with the new (Intel) motherboard -
so if there is another way to proceed I would be delighted to find
out.

And just to ask (with some trepidation) why wont this work

copy the Original 2003 CD to a folder on a PC
download the server 2003 SP1 and expand the file to another folder

run update in the SP1 to update the copied files from the Original
2003 CD

Create an image of the updated Server 2003

Create a boot CD and burn the image
Boot from "updated" 2003 CD which I now assume (perhaps incorrectly)
that it is now 2003 server SP1 and then make sure all the other
updates get installed in sequence..

Be gentle with me
"Susan Bradley" wrote:

Windows 2003 sp1 is what he's referring to.

Len, dear? I do not mean to be mean but I just gotta let 'er rip on
behalf of a potential client.

Is this for a personal setup or for a client?

If this is for a client can you please tell them to hit you? "the
logs tell me I just horked up this setup" that's what the logs are
telling you.

I speak from the voice of a customer here. Please I beg you stop
trying to cut corners and thus screwing up this install.

If you don't have slip media from Microsoft, PLEASE PEOPLE STOP
TRYING TO BUILD YOUR OWN. It doesn't work. nlite or whatever you
are using to build slip media doesn't work. You will end up with
the inability to add service packs.

The fact that the install messed up sharepoint is TELLING YOU this
is a screwed up box.

Please, I beg you, go back, start over do not build ANY slip media
and install this all over again.

Len Turner wrote:
Well - what a drama!

Please pardon my ignorance but why would I have to install Win
2003? Would that be a part of the 4 disk RTM set??

Anyway the saga to date

Could not install the original SBS Standard CD from the original
RTM all the way through - went all blue on me, as I said new (very)
intel motherboard

Read somewhare in the vastness of the SBS troubles blogosphere that
perhaps a solution would be to slipstream the SBS CD with SP1 - did
just that and created a boot CD with the slipstreamed SBS RTM with
an SP1 download and went through the whole install - including
disks 2 & (I think) 3 (sorry - its a bit of a blurr) from the
original SBS suite.

Activated over phone ok - glad i'm not dyslexic

Allowed the windows update thing to happen and downloaded and
allowed heaps of security update stuff to happen and then ahem..
"A nice SP2 is available to install - would you like to do so?"
Bugger - that was a silly thing to do - after the (long) install "a
reboot is required" so then the "You need to activate this software
(again)" happened.

No activation ID appeared so I rang MS and got shoved all over the
fn planet - each consultant telling me it was a technical issue and
passsed me on (from India to Malasia, back to India and the to the
states. The bloke in the states said I cant help cause you are from
Australia and after I jokingly reminded him that here in Oz we are
(reluctantly) part of the "coalition of the willing" he could treat
us Aussies as the 52nd state and give me a hand - he must have been
tired and emotional cause he hung up on me. those yanks are a bit
delicate - the Sub Continent help deskers a way more resilient to
frustrated callers.

Anyway next day got a freebie from MS (they wanted me to pay 500
bucks to help resolve an issue that I figure is MS doing but
commendably decided to waive the cost) and a "Microsoft
Professional Platforms Engineer" bloke called and advised me of
lots of tweaky things to do with bits in the activation files - no
luck

So I restatred the process - reinstalled the slipstream SBS/SP1 cd
and configured the lot again and then cloned the disk (lucky me)
and reapplied SP2 - bugger me the same deal - so now i am stuck-
Please excuse the long post but I am bordering on hysterical and I
just needed some one to sympathise.....

So my strategy is to create a combined SBS RTM/SP1/SP2 slipsteam
disk and try again but am I barking up the wrong tree?

BTW the setup hung up at first when it got to NIC install - told me
that 2003 didnt support shared NIC's (they werent) - disbled that
nag bit by stopping the netshare service but when I look at the
logs it tells me that 2003 doedsnt support Sharepoint 2.0 so i
uninstalled it so it may be that in slipstreamin i should also have
installed the othe server updates before going to SB2

anyway - thanks for giving the time - this site is a great resource



"Merv Porter [SBS-MVP]" wrote:

Did you install SBS 2003 SP1 along with Windows 2003 SP1/SP2?

SBS 2003 SP1 (full install) =

+ SBS 2003 RTM
+ Windows 2003 (SP1 or SP2)
+ Exchange 2003 (SP1 or SP2)
+ Sharepoint 2003 (SP2 or SP3)
+ a couple of other updates
+ SBS 2003 SP1

--
Merv Porter [SBS-MVP]
============================


"Len Turner" <LenTurner@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:3679B38E-5698-4EE7-B8BD-17230E93D51A@xxxxxxxxxxxxxxxx
I attempted a clean install of SBS 2003 Standard OEM on a rebuilt
server.
(new mobo) MS agreed that it was ok

Cannot install SP- 0 BSOD happens (probably newer hardware) so
slipstreamed
SP1 into the SBS Standard CD and then installs ok. Activate by
phone ok..

Set up server and Exchange etc etc then apply the SP2

Then get a "Must activate this software" nag so try to do so - no
internet
connection (there used to be) no installation ID number is
generated.

Snookered - are there some updates that are needed BEFORE
installing SP2 -

Can I build a slipsteamed SBS 2003 Standard CD with SP1 & SP2 to
create as
SBS Standard Server / SP2 slipstream CD for install that will
then accept my
activation key

Driving me nuts



.

Relevant Pages

  • RE: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • Re: FYI for eTrust AV 7.x Users
    ... When I just had my little incident with the redistribution settings on the SBS, my clients were logging successful checks for updates, and the logs indicated that no updates were found. ... That turned out to be because I had not gone back and checked the redistribution server box for 8.x after reinstalling the redistribution server. ... installed the new remote install utility which works the same as v7 did - just edited the .ICF file the way I wanted it and ran the client upgrades from the server. ... I can't remember if it's a separate install, or if you have to click a box when you do the Agent install, but redistribution server is not installed by default. ...
    (microsoft.public.windows.server.sbs)
  • RE: Monitoring and Reporting
    ... I understand that you unable to get SBS ... monitoring report after you install Windows server 2003 sp2. ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: SUS
    ... > I have setup a SUS Server on win2k. ... 0-2.reg will not configure your machine to automatically download updates from ... critical updates or service packs that your machine needs. ... It will also ask you if you want to install them, ...
    (microsoft.public.windows.server.general)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)