Zorba Posted October 30, 2011 Posted October 30, 2011 Hello All. I have read here that some of you are already doing this, so what am I doing wrong? When I associate a SIMS user with their AD account all looks fine. But when I try and save the changes I get an error message unable to find user joe.bloggs (eg). Any help greatly appreciated.
Sylv3r Posted October 30, 2011 Posted October 30, 2011 This is not something we use here, but I vaguely remember a post with this info included. Do you have the domain name as part of the userfield i.e. TEST\joe.bloggs Could be wide of the mark, but may be worth a go.
vikpaw Posted October 30, 2011 Posted October 30, 2011 Usually i'd ask are SIMS and the AD server on the same domain and network, and can see eachother? But if you are able to find them in AD and allocate, something must be going wrong on save. Are you on the new system manager now? Is there any more info in the error?
vikpaw Posted October 30, 2011 Posted October 30, 2011 I just tried on my test server and something has changed. It works fine on sysman 6 on my live SIMS running 7.138, but if i try on the summer 7.140 i get that error. What is happening is that the username going into the box is missing the domain part, which was working fine before. So i'm seeing "\bloggs.joe" whereas it should say "mydomain\bloggs.joe". Luckily you can type it in manually and it allows you to save. I haven't tried logging in like that, but i'm pretty certain it will work. @Sylv3r guessed right Did you log this with your support team? If not, we should get Capita to test it, and solve if need.
steve Posted October 30, 2011 Posted October 30, 2011 Have you tried within the new system manager 7 instead of old v6? Its been working fine for us for the last few months under the .net interface.
vikpaw Posted October 30, 2011 Posted October 30, 2011 Have you tried within the new system manager 7 instead of old v6? Its been working fine for us for the last few months under the .net interface. It's in sysman7 where i recreated the error.
Kyle Posted October 31, 2011 Posted October 31, 2011 We had the same issue, as soon as i put the domain name infront it worked ie; mydomain\joe.bloggs
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now