There actually is a way to disable scnotify or handle this situation (I just don't remember what it is off-hand). Torsten or Kenny would know off-hand.
J From: [email protected] [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Tuesday, August 27, 2013 4:24 PM To: [email protected] Subject: [mssms] RE: Over Run with SCNotify files on terminal servers/Citrix I figured it was possibly a common problem since Citrix is common. I can prune them with some kind of automation script, but that would be crap. Of course, we are possibly seeing Citrix step on WMI classes in root/ccm as a chronic issue, so I'm not a friend 'o Citrix at the moment. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, August 27, 2013 4:54 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Over Run with SCNotify files on terminal servers/Citrix Decommission your Citrix servers. (end of day, you didn't ask for a good solution, just what could be done) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Tuesday, August 27, 2013 3:38 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Over Run with SCNotify files on terminal servers/Citrix I just deleted 5,000 SCNotify and _SCNotify files from the SCCM client logs folder on a Citrix server. This was 300MB of files. What can be done to mitigate this? It was not the first time, so I don't think this is a one-off. Thanks. Ivan Lindenfeld Fidelity National Financial Jacksonville Florida
