Open the OST in Outlook, then Archive everything to PST.
Do I just add it as a data file in the mail area of control panel?
I don't think you can open it directly, but I could be wrong there.
I suppose a solution to this could be setup a VM as a jump box, put it behind reverse proxy and NAT, and lock it down as much as you can (SSH keys, etc.). From that jump box, access your servers. I do something similar with my colo lab server, except I just have Zero Tier on said VM, and connect to it via SSH over Zero Tier.
The above won't solve the problem of somehow having out-of-band management capability / console access, which you could have with IPMI.
Yes plenty of ways to do this the 'right way' but the I.T. company I was talking to doesn't get the risk of doing it the wrong way.
I was just running it by folks here to see if I was way off base by thinking they are nuts for making it public without any extra security.
Would you ever put a public IP on remote server management (such as HP ILO, Dell DRAC, Lenovo Xclarity, etc.)
What level of security risk is that?
Huge security risk. I cannot imagine that those things are actually patched and current.
That's my take on it as well. I was so taken back that I wanted to make sure I wasn't up in the night.
The easiest way I've found to get a GPO to update, is to one, set it to "update" and in cases like screensavers (backgrounds etc), literally just name the anything else.
"bg.jpg" the new one gets changed to "bg1.jpg" etc.
Trying to do this without the user touching GPO. I'm still fuzzy on how to set the GPO to update?
You only change the file copy GPO. I would have a different file name in your source file like 20180907_info.jpg. That way the GPO will process because it detects a change event. You can have the same destination file.
That would require editing of the GPO that applies the wallpaper.
It depends on how you set it up. My preferred method, and I believe best practice, is that you split your policies. The User policy applies the wallpaper based on <localpath>\picture.jpg. The computer policy copies the wallpaper from <remotepath>\20180907_picture.jpg to <localpath>\picture.jpg. When you need to update the wallpaper you place 2018xxxxx_picture.jpg in <remotepath> and update the policy to the new file name. When the machine reboots or refreshes its policies it copies the file from <remotepath> to <localpath>. When the user logs in the user policy is applied which uses the same file name (because as far as it is concerned nothing changed), but the new wallpaper is loaded because it is a different image.
Does that make sense?
Yes, so I need to point the wallpaper to load it from the computer not the server?
Yes, for the user policy it is the local path on the computer.
Kelly, when you move the file will it update if you don't update the policy with the new file name but instead keep the name the same in the wallpaper gpo?
So if you move photo.jpg from C:\Users\Public\ to C:\Temp\Shared? I'm not completely sure I understand the scenario you're describing?
What I want to do is to put a photo names info.jpg either on the server and have a GPO to point to that file to use as wallpaper.
Without touching the GPO that points to info.jpg I want the end user to be able to replace info.jpg with another file called info.jpg that has the same name but it's a different photo with the same name. Then the desktop updates on each workstation.
It seems like either copying the file from the server to the local workstation or pointing to the file on the server both require that you change the GPO for wallpaper and do a info1.jpg, info2.jpg to update the wallpaper GPO each time you change the photo.
I don't want the end user to mess with GPO but do trust them to simply save another file with the same name.
If you are allowing end users to change their desktop images why are you setting it via GPO? That is a lot of effort for little return.
As for your third paragraph I'm not sure how to answer what you're stating without restating my posts above. I guess I don't understand what you want to achieve as your end goal and what you want to avoid along the way.
I think you aren't understanding what I am asking. I'm allowing the office manager to put a jpg in a directory, that's it. Not the end users to change their desktops.