0

Previous to virtualizing our servers and using domain logins we had a practice of creating a wallpaper with the server name and services running on the server so if any technician logged in they wouldn't confuse what machine they were remoted into.

Now that we have 5x the number of servers and each technician using their own domain credentials, is there any way of obviously identifying the server they are remoting into similar to our previous practice?

My first thought was to create a GPO to set the wallpaper for all users, but I would have to create a separate GPO for each server, not to mention creating all of those wallpapers (that idea is out)

Maybe a login script of some sort could notify the user about the machines identity?

creative options are welcomed!

  • 5
    bginfo – jscott Aug 25 '16 at 18:53
  • If you grant RDP access to people who can't be trusted to know which sever they're accessing... well, that's your problem, right there. bginfo, different backgrounds or shell colors, and so on are a convenience, not something to rely on. This problem is best solved by removing access from people who can't handle it. – HopelessN00b Aug 26 '16 at 22:44
  • 1
    I dont need a shift in conversation @HopelessN00b. Suffice to say that all of my sys admins are trustworthy. – Brian Aug 28 '16 at 17:13
  • @jscott I successfully got bginfo up & running with this tutorial (youtube.com/watch?v=-HoO10Ke_6g), however I am stuck with the launch of bginfo.exe being halted by "Open File - Security Warning" is there a way around this? – Brian Aug 28 '16 at 17:15
  • @Brian right click bginfo.exe, choose 'properties', check 'unblock', click 'ok'. This removes the NTFS alternate data stream that says the file came from the internet. – jscott Aug 28 '16 at 17:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.