Did the hostname changer change how it works?
-
I wasn’t sure where to put this since it isn’t broken and this isn’t exactly a feature request. Before the new client version of FOG the hostname changer would change the hostname even if a user was logged in. However now in the log file I get a message that says a user is logged in and will rename it later after the user logs out. Could possibly have an option or something to let us rename even if a user is logged in? Or would that cause issues with how the hostname changer acts now?
-
The notification GUI your are referring to was not ready for the initial public beta. See [url]http://portal.fogproject.org/work_packages/24[/url] for the workpackage.
-
The client hasn’t changed. However I think the “model” behind it was a little broken because of the “randomly disappearing systems” setup.
-
I only brought this up because it used to work like that a some revisions ago. The old client would reboot the machine to change the hostname even if the computer was logged in. Then the first few revisions of the new client would have a pop up box saying the computer needs to rename and reboot and once you hit the ok button it would then restart and change the hostname. However these latest revisions seemed to have taken away that function.
-
[quote=“Wayne Workman, post: 44840, member: 28155”]IMO, it’s safer to wait until the computer is not in use…
Changing a computer name and forcing a reboot in the middle of someone getting work done will cause MUCH more than just I.T. problems…
I.T. maintenance should be transparent, even totally invisible to the end users… and should never prevent or disrupt productivity.[/quote]
for some computers, there is no time when they’re not “in use” as far as the computer understands. kiosks for example autologon and stay on 24/7
-
Powershell from a domain controller can immediately force computers to shutdown / restart / etc.
It’s incredibly powerful… let me dig up the script I use…
here:
[CODE]stop-computer -computername FirstCompName, SecondCompName -force
stop-computer -computername ThirdCompName -force[/CODE]You can also call a powershell script to run with admin rights using a batch file, like this:
[CODE]PowerShell -NoProfile -ExecutionPolicy Bypass -Command “& {Start-Process PowerShell -ArgumentList ‘-NoProfile -ExecutionPolicy Bypass -File "“C:\Remote_Shutdown.ps1"”’ -Verb RunAs}”[/CODE]
-
That option is for the task reboot service but not the hostname changer service. So unfortunately that won’t force the pc to reboot and change it’s name.
-
The shutdown will occur even when a user is logged in if you set the “force” setting on your FOG server. (I’m not sure where it is off the top of my head)
-
IMO, it’s safer to wait until the computer is not in use…
Changing a computer name and forcing a reboot in the middle of someone getting work done will cause MUCH more than just I.T. problems…
I.T. maintenance should be transparent, even totally invisible to the end users… and should never prevent or disrupt productivity.
