Not sure about the AD Auth in sims but you cna setup a trust so users on both domains can get onto sims.
Planning Trust Relationships in a Windows Server 2003 Environment
At the momment we have 2 networks, all the staff are on 1 and the students on another. We are going to be moving teaching staff off the staff network to the students network. The staff network will still have about 20 users. The staff network also has sims on the domain. The 20 users left still need to access Sims for the finance sims packages as well.
Is there away of 1st getting the staff users on the students network to access sims with the sims server still on the staff network. SLT want them still to use the sims client
2nd can the staff on the student network still some how use the AD auth that you can setup in sims system manager, or are all staff on student network going to need usernames and passwords.
Let me know you ideas please
I would look st a single domain where all users have accounts through the DC AD would then demote the admin server form any DC roles and join it to the curriculum domain as member server with static address to match, share the admin Sims folder with only staff access and map this as a drive that only the staff have access to.
All workstations built on to the admin domain need to be rebuilt onto the curriculum domain with sims workstation packages allocated to only the staff workstations.
Phew!!! hope this is what you meant ;-)
i would love a single domain. however slt want 2 networks, I am working on it to get one domain thow.
terminal server will do the trick
Beat me to it, was just about to mention that
For god sake don't change the domain name! You'll end up having to re-map the users (just hope all your sysman users aren't trusted)
nope none of our sysman user are trusted.
I did think terminal server, its just another username and password for them to remember. but ill have a look into it, simple to setup i know so ill have a go.
We combined our two networks last summer. All we did is move the SIMS server onto the new domain and used the same drive mapping. As we do not use trusted authentication SIMS does not care where it is.
During testing, we found we could actually connect across domains (from our test domain to the old admin domain), as long as we had a DNS lookup for the SIMS server.
I think they must reading the old Becta document, perhaps printing them the new one would help
There are currently 1 users browsing this thread. (0 members and 1 guests)