Hi we installed an SBS 2008 Server with 4 Clients Windows 7 (without SP1 at this moment). After we installed the Network we created Shortcuts on desktop to Prgrammfiles (".exe") stored on a Networkshare witch is connected by net use l: \\server\label\auftrag.exe /persistent:no A few times the icons are gone away, not in the basket not deleted by hitting delete or anything like this. The error appears once a week or once in 2 weeks and not on all clients. So we looked in to the Eventlog - nothing, absolutely nothing! But one thing.. It seemed to happen when the Computer is left alone for a "longer" time half an hour or so. First step is we tryed to recreate the Icons but the same happen again, then we disabled the Offline Data (because in one client we find an offline Data error in the logfile an the Icons of the Network Shares are red crossed). It happens again and again but we do not know what it is. Has had anybody else such a phenomenon?! Regards Volker

Hi, Thanks for posting in Microsoft TechNet Forum. First, you could try to disable the System Maintenance troubleshooter, follow these steps: 1. Click Start, and then click Control Panel. 2. Under System and Security, click Find and fix problems. 3. On the left navigation pane, click Change settings. 4. Set Computer Maintenance to Off. As you said, it occurred once a week, it may be related some Scheduler tasks, if this issue persists, you could try to disable Diagnosis scheduler task: Start Menu > Control Panel > System and Security > Administrative Tools > Task Scheduler > Microsoft > Windows > Diagnosis > Right click on Scheduled > Disabled Meanwhile, if you want to restore the current connections at each logon, you could try to use command net use /persistent:yes for test. Hope it helps. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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.

Hi Thank you, we set the first option on all Clients and will wait what happen! > Start Menu > Control Panel > System and Security > Administrative Tools > Task Scheduler > Microsoft > Windows > Diagnosis > Right click on Scheduled > Disabled I think this could not be the reason, beacause there are no rules witch this behavior is related to. > Meanwhile, if you want to restore the current connections at each logon, you could try to use command net use /persistent:yes for test. If the first one dosen't work we will try this Regards Volker

Hi, I am just writing to check the status of this thread. Was the information that I provided in previous reply helpful to you? Do you have any further questions or concerns? Please feel free to let us know. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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.

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Alex Zhao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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.

Hi at this time i think it will be "solved", but the last time i thought so it happend again three weeks later! Normaly i declare conservative, when something could be good, but in this case i think this should "solve" the problem. But before doing like me, watch your services and Hardware. What we have done does switch off the behavior not solve the problem in fact!! Regards Volker Frank