Sometimes you might see an alert from-
forfiles – a resource kit tool that iterates files in a folder, can do it on date, and let you then run a command You can get it here: ftp://ftp.microsoft.com/ResKit/y2kfix/x86/ http://technet.microsoft.com/en-us/library/cc753551%28WS.10%29.aspx This command should (I haven’t tested it myself) delete all files older than 30 days, under c:\temp and recurse into subdirectories. forfiles /p “C:\temp”.
After searching and trying a number of packet sniffers to determine the source of heavy traffic usage, I found this the easiest to install and use by a long way. Its reporting is excellent and it makes it easy to see the source ip generating a lot of traffic. http://www.colasoft.com/capsa/capsa-free-edition.php
Often you may need to remotely connect to a network workstion, but by default remote desktop is not enabled. Other than having an administrative user enable it on the workstation itself, here is a way to do it remotely. Run Regedit Select File | Connect Network Registry Enter the name of the remote computer and.
If Microsoft have pushed you into using desktop search as part of running office 2007 instead of search companion and you work on a network, you will have rapidly discovered how useless and time wasting it is. If you have connections to a number of network drives and don’t want to have the index service.
If you are getting event log ID Event Type:-
To permanently increase the default cache storage on offline files go to Start then click on RUN and type gpedit.msc the group policy window will come up. Drill down to Computer configuration\Administrative templates\network\offline files Click on Enable and specify the percentage of the amount of the hard drive space you want use for offline files.
Disable Data Execution Prevention (DEP) completely Click Start, and then click Control Panel. Under Pick a category, click Performance and Maintenance. Under or Pick a Control Panel icon, click System. Click the Advanced tab, and in the Startup and Recovery area, click Settings. In the SystemStartup area, click Edit. In Notepad, click Edit and then.
Windows could not start because the following file is missing or corrupt C:\windows\system32\config\system You can attempt to repair this file by starting windows setup using the original setup CD-Rom. Select “r” at the first screen to start repair. Do NOT use an OEM “Recovery Disc”. Only a valid Windows XP media will work or a.