Network client-server identity problem - on the network but not properly recognised

I have upgraded an XP x32 machine to Windows7 and everything seemed fine. But it isn't.

The machine has IP 10.X.Y.200 and the server has IP 10.X.Y.100. The client is present as a managed computer in the server management console.

However, the client is not recognised in Symantec Protection Centre and is unable to identify any network printers.

It can reach the internet and mail is fine.

The odd thing is that until about a week ago everything was fine and the client was recognised in SPC and could print.

The only thing that has changed in a new graphics card has been installed.

When I look at the event logs I see no print related errors. The only error I seem to get is a group policy one (copy of error message attached). All other Windows7 clients are recognised by SPC and can print to the network printers.

Finally, I can use mstsc.exe from all the clients EXCEPT the one I have print and SPC problems with.

Any advice gratefully received. WMI-error.txt
Marcus NTechnical SpecialistAsked:
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.

Cris HannaCommented:
well since you can't technically upgrade xp to Win7 you did a clean install, correct?
What version of SBS are you running?
How did you join the new Windows 7 computer to the domain?
0
Marcus NTechnical SpecialistAuthor Commented:
You're right, sorry for my loose language.

I performed a clean install of Windows7 x64 onto the xw8200 workstation that had previously been running XP x32.

After installation the xw8200 was in a Workgroup. I logged on as a local administrator and changed the Computer->Properties->Name and Domain Settings to add it to the domain controlled by the SBS 2003 R2 Domain Controller. That worked fine. (The xw8200 NIC MAC address has a DHCP lease reservation on the SBS 2003 R2 so the MAC was recognised and the computer, toghether with the change in meta data appeared correctly in the Server Management Console listing of Computers. It still does.)

I reinstalled all the programmes and, where I needed to get x64 applications, bought all the new softweare and installed that.

In fact, everything worked perectly (with the exception of WSUS for which I hae a currently open question).

The on or about the 29th September, coinciding with the change of the graphics card, the xw8200 stopped being managed by Symantec Protection Centre (which works with all the other Windows7 computers on the network) and I can no longer mstsc /v:SBSSERVERNAME /admin or print to a network printer.

Is there any way I can "repair" the Windows7 installation like I could do in the past with XP (from the Control Panel->Add/Remove Programs etc etc)?

What should I do to the registry to get more event log data as I don't think I am currently capturing the events that are resulting from theproblem?

0
Cris HannaCommented:
Two things
The Windows 7 machine was not joined to the SBS domain using the proper method...the ConnectComputer Utility does much more than just joining the domain.

Second..what happens if you remove the video card and removed the Video Card Software?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Marcus NTechnical SpecialistAuthor Commented:
The problem appears to be soething to do with group policies. I've put the output from the event log with this reply.

I'm going to remove the computer from the domain and then, from the SBS 2003 use the connect computer utility. What's the best way to do that?

I can't remove the video card as there is no on-board video on the xw8200 mobo and I no longer have the card that was there before. GPerrors-2011-10-10.txt
0
Cris HannaCommented:
before I suggest how to add to the domain
You may wish to save the profile or you may issues with apps working
Do you have other Windows 7 machines in the domain?  How where they joined?
0
Marcus NTechnical SpecialistAuthor Commented:
The network has over 20 Windows7 clients. They were added in two ways; either from the server, or sometimes by loging on to the local client as a workgroup administrator, changing the network settings to the domain (using a domain admin for authentication.logon) and rebooting.

It's only the xw8200 that has the problem and it really appears to be something to do with the group policies.
0
Cris HannaCommented:
If you look in ADUC, what OU is the computer located in?
0
Marcus NTechnical SpecialistAuthor Commented:
It's in my business -> computers -> SBS computers ... which is where all the other computers on the network are as well (single OU).

Could it be that WMI is corrupt on the client? WMI is automatic and started but the event log carries a WMI error message.

The message relates to GP {8A63E61B-F255-424D-88D7-4D984C213992} ... where do I find that?

0
Cris HannaCommented:
Should be able to find it in the registry by searching on that GUID
0

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
Marcus NTechnical SpecialistAuthor Commented:
OK, but when I find it, what do I do to it?
0
Cris HannaCommented:
The solution I would recommend is to disjoin from the domain...you can save the profile if you wish...
Then rejoin to the Windows SBS domain using the connect computer wizard...I would expect it to then go away.
0
Marcus NTechnical SpecialistAuthor Commented:
OK, is that done at the SBS server? Have you a link with step-by-step instructions that I can follow so I don't make a mess of things?
0
Cris HannaCommented:
Change the workstation from domain to workgroup (you MUST know the local administrator password for that computer (NOT the Domain Admin password)

Reboot

Log on to the workstation with the local administrator account

Right Click on IE > Run As Administrator

in the address bar type http://sbsservername/connectcomputer (obviously i hope you'll substitute the actual name of your sbs server)

Follow the onscreen prompts

Before doing this...I strongly encourage you to review the following http://support.microsoft.com/kb/926505
0
Marcus NTechnical SpecialistAuthor Commented:
OK, I have now resolved the problem. It had nothing to do with how the client was joined to the domain.

The xw8200 workstation is a Symantec Endpoint Protection client AND a PCTools Spyware Doctor client. That was fine in XP, but not in Windows7 (you have to delve into GPOs to discover this but I couldn't get the two applications to exist happily together).

The solution was to uninstall Spyware Doctor, reboot and, hey presto, xw8200 is a client in the SBS domain once again.

Thanks for all your help.
0
Marcus NTechnical SpecialistAuthor Commented:
Problem was an application conflict. Resolved by uninstalling one of the two conflicting AV products.
0
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
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.