Hi, I'm looking to clear up from the problems caused by the bug which created .TMP files on network shares. We have around 2000 users, and I have about 400 .TMP files on just one network share checked that need clearing up. The situation we face is, the files (.doc, .xls etc) replaced by .TMP's are stuck on client machines across the domain, in their Offline files. If we search for the .TMP files, each .TMP has an owner, so we can goto that person and make sure they resolve their conflicts so that the file that is stuck on their local machine is returned to the network in it's latest state. However, this is one network share of many. Does anyone know of any way of: Doing a search on Windows 2003/2000 servers, that will just return the .TMP file( the file name is 8 digit HEX), its owner and it's file path? Also, though I'm not sure this is possible, is there a way to automate all the effected machines to copy back files held in Offline Files(CSC) that don't exist on the network? On a side note, I tried using ????????.TMP NOT ~???????.TMP in a search on the 2003 server, which failed and returned everything on drive, I'm guessing this is a feature of Windows Search 4...? Update - I've checked another server, we now have a total nearing 600 files. I'm currently trying to pull a DOS based dir query through Excel to narrow down the exact numbers/users affected, but any advise or ideas on tackling this would be appreciated! I think I'll log it with MS too, as this was caused by a bug in Windows 7.

Hi, Thanks for posting in Microsoft TechNet forums. Have you applied the hotfix yet? Please make sure to update every Windows 7 and Windows Server 2008 to the latest service pack. Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Yup we've applied the hotfix. We cannot apply the SP yet, as we're just finishing a rollout of Windows 7, and the Service Pack has to go through alot of testing. We have alot of bespoke legacy apps here, so it will be weeks/2-3 months before the Service Pack is applied. We started the rollout before SP 1 became available. Either way, unless SP 1 actually copies things from the client CSC back to the network, I'll still be in the same situation. Anyone any ideas on a logical way to tackle this? Any automated way of doing this?

You can achieve this by using a scripting language such as VBScript. Please note that you will have to create the script of your own, but it is quite easy to follow. How Can I Determine the Owner of a File? http://blogs.technet.com/b/heyscriptingguy/archive/2004/10/07/how-can-i-determine-the-owner-of-a-file.aspx For the rest of the script, you can use samples from ScriptRepository: Script Center http://technet.microsoft.com/en-us/scriptcenter/bb410849 e.g. Search for Files Using a Wildcard Query http://gallery.technet.microsoft.com/scriptcenter/1ab41ec0-ad1d-4bc2-bdcb-992d169ee41f Other References: http://gallery.technet.microsoft.com/scriptcenter/site/search?f%5B0%5D.Type=RootCategory&f%5B0%5D.Value=storage&f%5B0%5D.Text=Storage HOW TO: Use the File Ownership Script Tool (Fileowners.pl) in Windows 2000 http://support.microsoft.com/kb/320046 [i havent tested this on w2k3] Sumesh P - Microsoft Online Community Support

Hi, Thanks very much for this, I did manage to get a full list of the .TMP files and owners using a DOS query, the problem I'm stuck with now is how to automate an Offline file sync that will copy the working documents back to the network. I've found that I could get an automated sync to specifically named directories (setting it to copy local info back to the network) however I have 400+ network directories affected, so that doesn't help, so unless I can wildcard the SyncConflictHandling under HKLM\Software\Microsoft\Windows\CurrentVersion\NetCache, I'm back to square one..

You can use the scripts from the above mentioned link to read off the registry and run the command to sync. Isnt that possible? Sumesh P - Microsoft Online Community Support

You should be able to use the SyncConflictHandling under either of the following: HKLM\Software\Microsoft\Windows\CurrentVersion\NetCache\SyncConflictHandling HKCU\Software\Microsoft\Windows\CurrentVersion\NetCache\SyncConflictHandling - Note that SyncConflictHandling is a registry key, not a value - you would then create REG_EXPAND_SZ values for each using the UNC path specifications as the name of the value, you can use a wildcard with the path specification, but limited and does not do full pattern matching, like this: \\server\share\dir1\dir2\file.ext would apply to File.ext \\server\share\dir1\dir2\* would apply to any descendent of directory “dir2”. \\server\share\* would apply to any descendent of “share” \\server\share\*\*.doc would apply to any descendent of share “share” with the DOC file extension. *.XLS would apply to any file in any location with the XLS file extension. * would apply to any file or folder. Equivalent to \\*, \\*\*, \\*\*\*, and \\*\*\*\*. - You would then set the value of each to determine the conflict resolution desired: Resolution = Value None = 0 KeepLocal = 1 KeepRemote = 2 KeepAllChanges = 3 KeepLatest = 4 Log = 5 Skip = 6 - These settings can be implemented either using a script targeting a machine or a user on the machine to add the values into the registry for the files - You can also implement them using a Group Policy Preference policy and adding the values - you would then subsequently remove the SyncConflictHandling policy from the registry after the conflicts are resolved using either another script, or by removing them via the GPP policy Hope that helps.Sumesh P - Microsoft Online Community Support

Superb Sumesh, thanks for that! I had found that Expandable SyncConflictHandling key previously, but it didn't mention that you could wildcard it, so I'd looked passed it as a fix, due to us having 350 directories to enter. Luckily, it's nearly all Word and Excel files, so we could stage that and clear up this mess! Thanks again! :-)