Within our network infrastructure we utilize a 2007 Exchange Server for our domain.
Today I was faced with a situation where a user who has MS Office 2010 x64 and utilized Outlook 2010 called me and stated that her "Saved Items" inbox was missing. I remoted into her system and sure enough one of her mailboxes was not present.
It's easy enough to "fix" this by just adding the data file again which is located on a network share F:..\mailxxx.pst
This user has multiple mailboxes as a way to view her archived data.
Located in this shared folder there are additional .pst files that remained accessible to the user.
This appears to happen randomly and has happened at least one other time to this same user, and one time to a separate user who also has data on this same share.
Thoughts?
Microsoft does not support PST files on a network drive. This is a recipe for a disaster.
Related
I'm converting a suite of legacy 32 bit C++ apps to run under Windows 10. These apps can run under different user accounts on the same PC and need to share the data between themselves and all the users. Some of the apps are Windows services, some are regular UI apps. There's a lot of communication between the apps and sometimes this is accomplished using shared data files. All the different user accounts need to access the shared data...
I have tried storing the shared data in C:\Program Files (x86)\Common Files\AppName\data
and have set the security level on that folder to Full Control for All users.
Most of the time, this works perfectly well. But occasionally, at seemingly random intervals, one of the shared data files ends up in:
C:\Users\UserName\AppData\Local\VirtualStore\Program Files (x86)\Common Files\AppName\data
I have tried to replicate this, and it never happens when I'm looking...
If I run a simple UI app that just writes to this folder, everything is fine. The App does not need to run with elevated privileges to write to the folder.
I suspect it's when one of the Apps is trying to write to a file that is locked by another, which the code handles by using exceptions, but Windows tries to help out by writing to the VirtualStore instead. But I could be wrong...
So, to cut to the question:
Where is the 'best place' to store shared data between several apps AND user accounts, that won't end up in the VirtualStore?
Andy
Any application with a requestedExecutionLevel node in its manifest is marked as Vista compatible and the redirection to the Virtual Store is disabled.
I have an Internet calendar (.ics) that I will sync with my office 365 account.
In the outlook desktop app, I can easily add an internet calendar with username and password, and I have the ability to edit the sync interval (1 min) - working fine.
My problem is now, I can't see this calendar on my Smartphone.
Adding this calendar in outlook.com (also in the cloud) doesn't work because MS only allows public ics calendar (why MS why?).
I can copy the internet calendar in outlook desktop app to my "own calendar" but then I have only a snapshot not the sync internet calendar...
Is there a solution for my problem? I can't publish the calendar without password and username...
Cloud-based syncing services: Web apps like Dropbox, Apple's iCloud, and Microsoft's Live Mesh synchronize folder(s) among your devices while saving copies of the shared folders online. Changes made to files in that folder from one device automatically get updated on the others. You can also enable file sharing, use a mobile phone to access the files, and in some apps, open the files on the website.
Desktop applications: If you're not comfortable with your files being stored online, you can install software that synchronizes files locally or over a private network. Shareware and freeware file-syncing applications include GoodSync, Microsoft's SyncToy, and SyncBack. Besides offering more robust options for file syncing (keeping multiple versions of replaced files, setting a schedule for syncing compressing or encrypting files, etc.), these programs also typically allow you to sync with external drives, FTP sites, and servers. Take a closer look at these and other syncing apps in a roundup of the best file syncing apps.
More information here
Also specifically here is a video explain how to share colander across all your devices click here to watch it
We've transitioning from Rackspace dedicated boxes to a completely cloud Azure environment. Production servers and development and as an MS shop we're going to be using Visual Studio Team Services. As an MS ISV partner we have a bunch of MSDN seats so our developers are all going to have an MSDN w/ VS Premium account which we'll use with Team Services/TFS. We're replicating our production web server on a virtual machine but after some refactoring will eventually move to an Azure website.
My question is about when users leave the company. Right now we have everyone log into a development server using RDP. They develop on that server. When someone is gone we shut their access off to that server.
With Team Services when the user opens up a project do they automatically get the entire project downloaded to their local development environment/machine? If someone leaves the company is there a process using VSO that secures that code and removes it from them or makes it inaccessible? Any way to lock it down when we need to? I can't seem to find a procedure to do this.
To add or remove someone from the account, go to the Users hub on the home page for your account. If you remove a user from it, that user will no longer be able to access your account.
When users connect to your account, they'll need to take some action to get source code. That would be cloning in the case of using Git or creating a workspace and running get for TFVC.
If the user has source code, for example, on a machine, there is no way to remotely remove it. They won't be able to get updates, etc., but there's nothing running on the computer that would be able to erase the code the user has already obtained.
All source code sharing i know allow zipping up or browsing the local repository. Including VS Team Services.
Daniel Mann is correct . Developing on shared servers via RDP is terrible for productivity due to development being graphics and disk intensive, often requiring admin rights and reboots / crashes, debugging triggers system interrupts, out of memory loops are fun on a shared machine ie they stuff everybody else around. (Even with RDP you can copy and paste or map a network drive locally or upload to the net )
If your doing critical stuff the ONLY thing that really works is physically bring them in to non internet connected machine /network with USB disabled. However these mechanisms especially denying internet will half productivity.
This is why most organizations rely on legal contracts. On a 2M project is it worth making it a 4M project? There are cases where this is required normally around national security /CIA / Defence but not for IP, there are better / trickier ways.
Pretty much all binaries are reverse engineer-able with little effort if you really want to. obfuscation does very little.
Alright, so here’s the situation:
First, I’ve implemented a WSUS server and GPO to prevent/keep and centrally managed our windows update systems and the only updates I push out automatically are Critical updates, service packs, and Security Essentials definition updates. These take place at 8:00pm nightly with the exception of MSE which happens every hour if they are available.
This morning 2 of our managers, one is customer service the other accounting, and one of our sales reps, came in to find their POP3 outlook 2010 PST files gone. Just completely not there. Because we use folder redirection, all PST files are stored in appdata\local\microsoft\outlook in the local user profile (no roaming profiles just redirection at this point). I took an image of the accounting machine using FTK imager and the location of the PST is there and the file is there. Curiously, the 2 archive files are recoverable and working after an export. However, the main pst that was 5.9 GB was reading 0 bytes. I took 2 more images and all report the same thing, that the main pst is 0 bytes. The last modified time was 8:17:41pm yesterday 8/14/2012.
I started the imaging on the other two machines and will know more about those tomorrow.
All folder redirections and GPO according the event log pushed out successfully. Several of the KB updates (I forgot to bring them home), totaling 5, had to do with Office Home and Business 2010 Single Point Image (according the event log). It pushed out to all 35 machines successfully without 3 machines having this outlook issue. Two of these machines were infected with a Maclicioustool:win64/spector Trojan/virus back on 7/3 when MSE quarantined and deleted the file.
Any ideas on where to start so I can give my bosses an answer?
Couple of ideas/thoughts. One, ensure antivirus agent on them is fully updated and functioning, then run a full, invasive scan, with every A/V option turned up, "full tilt boogie" to catch anything - but do it from a bootable CD so you aren't loading anything malicious from the OS.
I'm guessing the OS is Win7, which runs something called Volume Shadow Copy, which uses System Restore Point. At this point, pull up the VSC history, and I'll bet that's where your original .PST's are located.
Also, I trust the version of Office is 2007 or higher. 5.9 GB PST is way too large for Outlook 2003 and would likely be corrupted. And folder redirection to a local folder on the host has nothing to do with files disappearing, but you probably already knew that. :)
I'm building a product that involves
a windows service caching data on the local machine,
user processes reading that data and writing their own data,
the service in turn writing back that data to a server.
Where should I put the data files for this, such that they'll be shared by all users and read/writable? The software will operate in a corporate environment where desktops are sometimes pretty locked-down, so for instance some users won't have write rights to C:\Program Files.
I don't think C:\Documents And Settings\All Users\Application Data\ is a good candidate - I think by default only Admins & Power Users have write access here.
I could use each user's Application Data folder, but this would be a bit of a pain as different people could use each machine ... so it'd be simpler if there was just one shared location.
I'm developing in C# .net 2005, but that's probably not too relevant.
Unfortunately you have no real choice. You must (you really must) call SHGetSpecialFolderLocation to get the path to c:\users\public\AppData (which is the name of the folder you linked above, but on Vista and possibly Windows 7)
Then you MUST create your own app folder therein. And then, you MUST, use the security APIs to modify the ACL of the created folder.
There is NO folder on the system with a default ACL that allows multiple non administrator users to read AND write the same files.
c:\users\public\AppData is the closest. Modifying the ACL of a application folder here seems the best approach. Of course, once one has resorted to ACL modification, the folder really could be created anywhere at all. But that could surprise system administrators and result in weired security holes.