Here's the scenario:
Consultant calls me, he can't create a database backup because the wizard won't let him browse the local disk. I remote into the server in question (Windows Server 2012 R2, SQL Server 2012) and verify the problem. I ask if I can restart SSMS and I can. I make sure to launch SSMS 'As Administrator' (he was already logged on to the Server with Domain Admin rights) and connected to the Instance. Here's where it gets funny... The connection was set to connect as a SQL User, not with Windows credentials. Same problem. I disconnected and reconnected with Windows Credentials and, everything worked as planned.
Now, this Consultant - he's no dummy. He was actually our Director until January when he retired. (He's back because some projects didn't completed and, he's the only one who knows some of the Legacy applications -...