cloning on a non-domain network

non-domain microsoft network with 8 XP computer systems
no server on the network, only using as400 system for parts lookup, etc.

I just cloned a system from another exact computer using ghost 7.5.  All works well after changing the computer name except for logging onto the AS400 system for parts lookup.  I can browse the shared folders on the network and print to network printers, etc. and browse the Interent/email.
Is there anything else I should do with the system so there are not conflicts with logging into the as400.   I have read about sysprep but do I really need to do that if not on a domain network?
There seems to be one problem with our AS400 login and maybe that relates to the clone issue.  Thanks.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Yes, you really do need to do that, otherwise you'll lose Microsoft's support; I'd suggest to create a proper deploying image on which Sysprep has been run, then try again:
"Microsoft does not provide support for computers on which Windows XP is installed by duplication of fully installed copies of Windows XP. [...] If an image was created without the use of sysprep, Microsoft does not support the running of Sysprep after the image is deployed as a way to bring the computer back into compliance."

The Microsoft policy concerning disk duplication of Windows XP installations
Hi krusebr,

what leads you to not want to use sysprep?

its only been in the last year or so that i have actually started using the tool again as before xp you could work around issues wth not using it - but its a simple and easy process to go through and additional to that as oBdA has already pointed out - you are no longer working on machine thats unsupported.... sysyprep takes about 10 minutes of extra config per machine...  certainly worth it in my opinion

Support wise, it's a valid point.

Other than that, you don't need really sysprep if you're NOT on a domain network... but I'm also assuming that you're using a volume license and staying within the legally allowed number of machines. But also make you you read oBda's article just so that it can't be said you weren't warned.

Your AS/400 issue sounds like something that was set into the machine that you chose to close in the first place. Start up the AS/400 client and look in the settings? Is there a workstation name already set into there? If so, delete that workstation name and save the settings.

When there is no workstation name set, AS/400 servers will automatically assign one. If you have one set already, it will just use the one you picked. That can lead to conflicts whenever you try to sign in.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

BTW - close = clone

So if your problem is something like the workstation name already being taken, that should resolve your issue.
krusebrAuthor Commented:
Yes, we do have volume licensing.
Never have had to use sysprep on non-domain networks before and never on a 250 system Novell network.  If I don't have to spend 10 min. per machine...?why?  Do not use MS support.
Masnrock solution worked.  Thanks.
Thanks to all who responded.
There is an approach to answering things after using Sysprep where you can have an answer file on a floppy disk, which would cut down big time on that 10 mins.

However, I've also experience times where using Sysprep has also forced me to go back and have to reinstall certain applications. So I don't mind sysprep when it's something like computers being used pretty much like dumb terminals (but then that defeats the purpose of a PC!)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.