Undoing Changes to Windows Server 2012 Roaming Profiles

Dear Experts,

At some point I followed some directions and altered our server in a way I have no idea how to undo. I enabled the roaming profiles, and I'm pretty sure the only reason I did it is so we could get remote desktop services to work, because we wanted to be able to see which users were logged in. Ultimately we were hoping to be able to control other people sessions so I could drop in on their session and help them with errors and stuff like that. But it turns out that you cannot do that on windows server 2012, you have to have R2. So it was a complete waste of time to install all of that as near as I can figure.

At this point we've realized we really don't want roaming profiles. I'm not sure if I need to uninstall the RDS too, but I do know that we all log in to the server to use it, using remote desktop. So I'm uncertain what features there I need or don't need.

Anyways, can someone please help walking me through disabling the roaming profiles?

It is also possible the issue I'm running into may be the "user profile disks". I'm not sure what they are exactly, but they seem similar to roaming.. This could maybe be it too? If that's the case and I just want users to be able to remote in and use their regular profile (not roaming) do I need to somehow remove the rds collection to fix this?

Thanks very much! ~Jeffrey
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.

Lionel MMSmall Business IT ConsultantCommented:
Roaming profiles is easy just go to the user profiles tab in AD Computers and users and remove the profile location settings. And no you do not have to remove RDS  as that is not related to roaming profiles. Roaming profiles are basically there so that if a user logs onto more then one system that the look and feel of their desktops follow them from system to system. RDS it its most basic sense allow you provide applications (programs, apps, virtual machines) to multiple users from one central resource.

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
JeffreyDurhamAuthor Commented:
I guess it really isn't roaming profiles, but the user profiles disk thing, which is similar to roaming profiles. I guess when I set it up awhile back I must've had to create a RDS Collection, and on that collection I had a setting set to turn on the user profiles disk.

Yesterday, I tried undoing that and it turned out to be a disaster. All the profiles started getting corrupted and then overwritten, and we had to literally recreate some of the profiles.. which resulted in a lot of temporary profiles also. I ended up having to turn the user profile disks back on.
I'm wondering if the approach would've also been to remove the rds collection.

I would love to know how to turn those off without destroying everyone's profiles, but I think I may pose that in a new question since I asked about the roaming, and take your answer, as that is the right way to go about the roaming profiles. But on the users themselves in the AD Computers tool, I checked that out and we don't actually have any of them set to be roaming.

Thanks! ~Jeffrey
Lionel MMSmall Business IT ConsultantCommented:
Well user profile disks and RDS are related--these are virtual disks associated with certain profiles--it is like having a drive to store user data and settings so if you were to turn these off it would cause problems so the question is why did you turn them off? Did you want to do something differently?
JeffreyDurhamAuthor Commented:
Yeah, we didn't really want the user profile disks. I actually set it up originally because the instructions I was reading said I had to for the collections. We needed the rds collections because I wanted to be able to remote control other people's sessions. In the end it turned out in windows server 2012 you can't do that, you must have the R2 version. We're actually talking about buying that today, I'm just looking into now whether or not we can transfer our rds licenses from the 2012 to the 2012 R2.

So far we've noticed that the user profile disks make it so that chrome doesn't work right, not allowing you to install extensions, and some of my code has had issues with returning the right user name that is currently associated with the logged in user. I'm not positive that has anything to do with the user profile disks though.

My goal was to try to revert the server back to what it was before I installed the extra rds services that we didn't need, and just have regular user profiles that people log into. We only have maybe at most 15 that would be logged in at a time, so we wouldn't need to do anything crazy like set up different groups of people in different collections anyways (I think that's what those are actually for, not sure :).

Not sure how we're going to approach it from here. We were thinking of either setting up the server 2012 again on a different hard drive over the weekend or trying to get the R2 and figuring out how to migrate our stuff over to it.
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 Server 2012

From novice to tech pro — start learning today.