The WinRM service failed to create the following SPNs: WSMAN/; WSMAN/BRPRVNW01.

Ok, just upgraded the 2008 servers to 2012 r2 via clean install added ads. Again the above error occurred as it did in 2008 did the fix via adsi edit "network service grant permissions etc" didn't work (did In 2008) still error flashed up, so I used the setspn util. it registered the entries fine, but the error still keeps recurring. Can I take it that its ok just to ignore the error now the entries are registered, and its just one of the buggy ms software messages?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Cliff GaliherCommented:
The errors can be ignored. But it is not a bug. The system attempts to register SPNs every time as a self correction. So the permissions blocking the registration are indeed a legitimate issue causing the error. So since you manually registered, you can ignore the specific error, but it doesn't mean the error doesn't exist. Somewhere you have permissions blocking automated registration in AD which is why you had the error in 2008 and why it followed you to 2012. It replicated with AD.
brookejpAuthor Commented:
thanks the setting for the network service is set to allow validate write to service principle name in adsiedit  , but again rebooted and the warning again popped its head. Did this in 2008r2 to correct the error and the warning disappeared but in 2012 its just keeps on insisting to show it... mind boggles.
brookejpAuthor Commented:
Cliff GaliherCommented:
Like I said, you can safely ignore it if you manually registered. If you really want to fix it, it could be a number of things (dozens) and I'm not sure I could walk you through them. I just wanted to clarify that it isn't "buggy" as you described. It is reporting a legitimate permissions issue.

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
brookejpAuthor Commented:
would have like to fix it.. OCD lol - but I can sure live with it. for the time being.. going to be putting exchange 2010 on another server so I was worried It may effect its function. but ye can live with it.. thanks for the help much appreciated.
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
Active Directory

From novice to tech pro — start learning today.