Problem: Change Machine Display name reverts back after reboot.
Cause: Registry key not staying set on student machine
When a PC Student is first installed, the Machine Name that is shown for that Student, by default, is whatever has been set as it's %COMPUTERNAME% environment variable. Often when student computer images are created by an automated process, this Computer Name will be a machine generated unique identifier, like "AMS-640381", that doesn't mean anything to a human Teacher.
When the Teacher uses the "Change Machine Display Name" feature and sets a user-friendly name for a Student machine, it saves that alias to the "MachineName" value in the registry of the Student PC [ \\HKLM\SOFTWARE\Wow6432Node\LanSchool\MachineName (On 64-bit PCs, remove the "Wow6432Node" key for 32-bit PCs) ] If the "MachineName" value exists, then whenever a Student machine is discovered, it will give this as its Machine Name instead of the cryptic ComputerName. Having it saved on the Student side is nice because anytime another Teacher or Tech Console discovers that Student, they will automatically see the new user-friendly alias, like "Linquistics Lab - West Wall #4" instead of the old non-descriptive ComputerName.
This is often confusing for Teachers, because nearly every other setting that the teacher changes in the Teacher Console is saved locally on their teacher machine. Those settings persist from one reboot to the next, without fail. However, it's a common practice for the student PCs to be setup with "workstation protection" software, like DeepFreeze, that will undo any changes and revert the PC back to its frozen image each time the machine is rebooted. Even though the Teacher uses the "Change Machine Display Name" feature on the Student and set's it's alias to a user-friendly name, after the Student machine is rebooted, it will once again be reverted to a state where that "MachineName" registry key doesn't exist, so the Student will report its Machine Name as being the ComputerName again.
How to display the MS AD LDAP Settings being used.
The following comes from the URL : http://support.microsoft.com/kb/315071 This step-by-step article describes how to manage Lightweight Directory Access Protocol (LDAP) policies by using the Ntdsutil.exe tool. To make sure that domain controllers can ...
Change OTP Issuer Name
Issue When a user configures an authentication app, such as Google Authenticator, for OTP, the entry is saved in their app with the issuer name of Lenovo Software. Is it possible to customize the Issuer name to our institution? Solution As of ...
Login Script to set display name and channel based on csv
This script will require you to create a .csv that contains the machine name and the desired channel. It will then will take this data at login and configure the student's display name and channel properly. We do not provide direct support for this ...
Display domain policies on a machine
How can I find what policies are set on a machine based on logging into my companies domain ? Start, Run, rsop.msc This will load the snap in and allow you to see what policies are applied to the workstation. Other handy tools : gpedit.msc - Edit ...
User not able to change password in Unified Workspace
How to enable Change Password debug, when having trouble with users not being able to change, or reset, their password in Unified Workspace. The Change Password debug needs to be enabled on the server that connects to your directory. You may know ...