Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 265
  • Last Modified:

Add Remove wizard problem

Hi,

I have a client who has migrated from SBS 2003 to a new server with SBS 2003.

When I click on Add/Remove for SBS 2003, it goes through some checks and haults at this error:
"windows sbs 2003 error the computer cannot be upgraded to the oem version of windows small business server"

I spoke with Microsoft and they said that it is the customers fault. The customer had copied the Microsoft WIndows Small Business Server folder and Windows for Small Buisness Server folder from another server to this new one. The reason? Because they wanted to use the server managemnet snap in.

Apparently, SBS Add/Remove is now picking up these folders (created on a server in the year 2003!) and not allowing customer or me to go any further.

Microsoft said said we have to reinstall the entire server. This is not an option.

Does anyone know a work around?

Thanks
0
bestchoiceit
Asked:
bestchoiceit
  • 2
  • 2
1 Solution
 
Netman66Commented:
If MS is telling you that's the only fix, I can assume they know what they're saying.

The only thing you could try is an inplace upgrade off the correct CDs.

Other than that, it's not your fault and they'll have to pony up to fix it.

0
 
bestchoiceitAuthor Commented:
Hi Netman66,

Somehow I was not convinced with the engineer I spoke with. He kept going off for 10 minutes and coming back.

I am convinced that either with a regedit or deletion of some files that I can get beyond this wizard error/warning. I just do not know if it's possible, how and which entries....
0
 
Netman66Commented:
If what you're saying is true (about the copy of folder structure from another server over this one)  then it's anybody's guess what is necessary to bring this back to life.  Even if you did get past this error, what else is broken?  I, personally, wouldn't try to hack this back to life at this stage.  If you're contracted by the client, then the exposure to litigation should something go wrong may not be worth the risk to you.  You're better to do a controlled rebuild so nothing gets lost or broken.  That's my personal opinion.

The Support person was likely back and forth with an Engineer on the problem and this is why he kept disappearing.  These front-line people only have scripts to follow.  When the issue gets outside the script they call up and Engineer and work it.  Generally, then escalate the customer up to Engineering rather than play phone tag, but anything is possible I suppose.

0
 
bestchoiceitAuthor Commented:
This question has not been answered yet - if no one has the answer, I will re-install the server tomorrow.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now