Hello, We have noticed that the SCOM R2 Console (not web console), creates tens of thousands of zero byte .tmp files in the user's temporary internet files folder. Deleting these temp files takes upwards of 30 - 45 minutes and slows down performance of the console server terribly. Additionally, the console does not clean up after itself (even using the /ClearCache parameter) and eats up our disk space rapidly. Is there a way to prevent the SCOM console application from generating so many .tmp files under the temporary internet files directory and/or deleting its files upon closure of the SCOM console application? Example: User A has been using the console server for one month and the following has been found: C:\Documents and Setting\UserA\Local\Settings\Temporary Internet Files\Content.IE5 directory has two subdirectories (random chars comprise the directory name) with 85,000 tmp files in one directory and 55,000 tmp files in the other directory. The files are 0 bytes in size but eat up ~450MB of allocated disk space. This user does not use Internet Explorer at all on this server. So, my best guess is that the SCOM console uses the IE rendering engine and creates all of theses files during operation. The console server is running Windows Server 2003 SP2 (32-bit) Standard with 4GB of RAM and a 40GB C:\ drive. We average about 10 RDP sessions daytime -- each with the SCOM console application open monitoring our customer environments. Any ideas or suggestions would be much appreciated. Thanks in advance. -Jorge

Oh c'mon, somebody else has to be experiencing this problem. I surely can't be alone on this one. This a default SCOM 2007 R2 console installation from the R2 media. I checked the SCOM 2007 CU2 release notes, but I didn't see any fixes that necessarily addressed the large amount of temp files created by the console application issue. Any SCOM MVPs have any thoughts or ideas? Many thanks in advance. -Jorge

I'm sending mail over to our UI test team to see if anyone has seen this before. This sounds familar to me, but I don't recall what the solution is. Your scenario here is that you have a Terminal Server that ~10 users RDP into and open the Operations Console right? What version of Internet Explorer is installed on this machine? Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Yes, that is correct Michael. We have IE version 8 installed (build version 7.0.5730.13).

Hi Jorge, I think you can try Process Monitor and see if there are any “.tmp” files created by SCOM R2 Console or if they are created by other programs. Process Monitor v2.91 http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx Hope this helps. Thanks. Nicholas Li - MSFT 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.

Thanks Nicholas. I was able to use Process Monitor to verify my suspicions. The Microsoft.MOM.UI.Console.exe process is in fact responsible for the tens of thousands of .tmp files created. I am hoping to hear back from Michael as to what fix the UI team has for this issue.

I've had similar problems and lots of crashes when the console is running as a user account with an exclamation point in the name, like: USER! I know it seems strange, and it took a long time to figure that one out, but after creating a special user account to run the SCOM console, most of the strange problems went away (it still has lots of bugs though). HTH

I can see the tmp files as well. However i don't have 10.000's and when i close the console they disappear. When you do a "dir /a /s *.tmp" on the "Content.IE5" directory then close the console does the number of files drop? It could be tmp files from previous console sessions which aren't cleaned up for some reason and never will. Rob Korving http://jama00.wordpress.com/

Steve -- Thanks for the tip but we don't have any user accounts with uncommon characters like '!'. Rob1974 -- If I do a directory listing as you specified, I do see the tens of thousands of .tmp files the console created and did not clean up after itself. I just performed a test and only 2000 out of 44000 .tmp files were deleted when I closed the console. So, we need to know the root cause for why the console leaves so many .tmp files behind.

Some suggestions: If this machine has any anti-virus or anti-malware installed, try disabling it or exlcude the folders and/or MOM console executable. If the machine has a backup client with an open file agent, try disabling that.

Steve, Thanks but this machine (a VM actually) does not have any anti-virus, anti-malware, or back agent installed. - George

Does the VM have all of the latest updates for Windows, IE, and MSXML?Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Yes, we recently built it in late June and applied the latest Windows, IE, and MSXML updates that were released at that time. We have not applied any July updates as of yet.

In the meantime, I have created a batch file to delete all the .tmp files in my user profiles folder. For now, this is keeping a handle on the disk space usage. I would really be interested to know if other customers are experiencing this problem with the SCOM console.

Dan, I don't think my temporary solution is the answer to the problem I am experiencing with the SCOM console. I need a permanent fix to prevent the console from leaving any files behind upon exit.

Question: When the users connect to the Terminal Server to use the Console, how do they "exit"? Do the close the OpsMgr console and then disconnect the RDP session? I'm wondering if they close the OpsMgr Console and THEN disconnect the RDP session if that would resolve the issue? Its possible that the console never gets a chance to clean up after itself. I'm no TS Expert, so this is a guess based on how I think it might work.Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

it's not written in the system's temp, but in the user's temp. it wouldn't explain why it wouldn't clean up jorge's tmp files.Rob Korving http://jama00.wordpress.com/

Ok, so the .tmp files go into the user's temp directory. If the User that is connected to the Terminal Server "closes" the window that has their TS session open, what happens? Does our console get a chance to kill those files?Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Correct. Our users close the OpsMgr console application and then logoff their RDP session. The .tmp files remain in their user account's IE cache. If the user "closes" the TS session without logging off, we have TS configured to leave their session running so that they can reconnect -- i.e. we have the idle timeout set to 'never' and do not 'disconnect' the user in our TS configuration preferences. - Jorge

Hi, No activity for a long time, will mark as answer. Feel free to re-open. ThanksAnders Bengtsson | Microsoft PFE | blog at http://www.contoso.se