However, since the user profile was restored, the corresponding shortcuts were still on the desktop. As expected, applications I previously installed disappeared. In my tests, rebuilding a WorkSpace took between 12 and 20 minutes. WorkSpaces also doesn’t remove the old computer object from Active Directory you have to delete it manually. Thus, if you moved the computer object to another container, you have to change the OU again. However, after the rebuild, the computer will have a different name and will appear in the computer’s OU. The user object will remain in the Active Directory container to which you moved it.
#Amazon active users password
For instance, the user name and password of the WorkSpace will stay the same. Some directory-related settings will not be affected when you rebuild a WorkSpace. Also notice that data stored in locations other than the user profile, for example in a folder on C, will not be restored. Thus, if you have to rebuild a WorkSpace and want to ensure that all user data is restored, you should wait at least 12 hours after the user last logged on, or you should create a backup of the user data yourself.
If a user messed up a desktop, you can rebuild the WorkSpace through Amazon’s management console.ĭata in the user profile will be restored after the desktop is rebuilt however, user data that was saved within the last 12 hours may be lost. Instead, you use the Amazon web interface to add new WorkSpaces. For instance, you can’t deploy desktops with your imaging tools. There are some obvious differences in the way things work with WorkSpaces. Please reset your WorkSpaces credentials WorkSpace rebuild ^ Users who forget their password can reset it by clicking a link in the WorkSpaces client.Īfter the user solves a captcha, an email with a link for resetting the password is sent to the user’s email address. For example, a user can send a “CTRL+ALT+Del” through the WorkSpaces menu and then select the “change password” option. However, users can change their password once they log on using the common methods. I guess the WorkSpaces client simply doesn’t allow the user to enter a new password. After I reset the password without this checkbox enabled, I could log on again. I figured that problem was related to the “User must change password at next logon” option of the password reset applet. For instance, when I tried to reset the password of my WorkSpaces user in Active Directory, I could no longer log on.
I am afraid that many of those differences will become obvious only when you work a while with WorkSpaces. Of course, there are also differences if you run virtual desktops in the cloud. I also saw two domain controllers, but access was denied when I tried to connect to them with the Computer Management console.
I was even able to connect to those machines with the Computer Management console. I saw several computer objects of workstations in the computer’s containers I didn’t provision through the WorkSpaces interface.
#Amazon active users install
You have access to Group Policy, you can install WSUS for patch management, and you can also install third-party management tools for software deployment or whatever you need to manage your WorkSpaces.īy the way, it appears Amazon pre-provisions WorkSpaces. You can essentially do everything in the WorkSpaces AD as in your on-prem AD domain. WorkSpaces Active Directory domain controllers
0 kommentar(er)
