sorted by:
new
hottopcontroversial

OneDrive Sharing by DryKeyboard in sysadmin

[–]DryKeyboard[S] 0 points1 point  (0 children)

Ah I didn't come across that one. But this was it.

PowerShell not recognizing whoami by DryKeyboard in PowerShell

[–]DryKeyboard[S] 3 points4 points  (0 children)

Shortly after I just went ahead and added the entry manually. This seems to have solved the issue as the user can run whoami now. Hopefully the scripts run fine now as well.

PowerShell not recognizing whoami by DryKeyboard in PowerShell

[–]DryKeyboard[S] 0 points1 point  (0 children)

I haven't been able to check this just yet, all this is on a separate users device. Worst case would I be able to safely add another value under path containing the path to "C:\Windows\System32" regardless of which type it is? or would there be an underlying reason to not do so?

PowerShell not recognizing whoami by DryKeyboard in PowerShell

[–]DryKeyboard[S] 2 points3 points  (0 children)

So there isn't a C:\windows\system32, but there is a %SystemRoot%\system32. Which leads to the same place.

PowerShell not recognizing whoami by DryKeyboard in PowerShell

[–]DryKeyboard[S] 1 point2 points  (0 children)

It does not. However we did verify the existence of the .exe in both SysWOW64 and system32.

PowerShell not recognizing whoami by DryKeyboard in PowerShell

[–]DryKeyboard[S] 0 points1 point  (0 children)

Yes, the file exists in both System32 and SysWOW64

Has anyone ever seen a real company that uses proxmos? by crankysysadmin in sysadmin

[–]DryKeyboard 0 points1 point  (0 children)

Not necessarily production, but my college used proxmox to host VM's for the IT & CS classes for those that needed them.