A few things that SMS disrupts: 1) screensaver: our IT folks force a screen saver with password; we end up disabling in order to run tests on the target embedded system -- long periods of inactivity where we are just collecting or monitoring data and then the screensaver comes and if you are not present to enter your password, nobody can see. So you either give out your password, which defeats the purpose, or turn off the screensaver. But then as soon as you reconnect to the network they turn it back on. 2) QNX Boot File; I have a Windows 2000 Professional partition and a QNX partition. I have a boot-up script that, upon power-up, allows you to choose the OS for boot-up. SMS activity (we suspect Norton Anti-virus scan) sometimes comes in and undoes that feature, and we can't get back to QNX. 3) We use these laptops for autocoding application software; then put the .c and .h files over to QNX side and compile; load onto target and then test. With SMS running, autocoding takes a lot longer than if not.
These machines are not used as Desktop Stations, rather as Portable Test Units. But our IT folks don't have an option in their scheme to omit SMS programming, so we've just done it ourselves. Windows 95 and 98 were easy. Could either boot-up in DOS or QNX and prune the SMS directory; put a dummy file in its place and no more SMS activity. But QNX 4.25 does not recognize a NTFS file system. DOS doesn't work either. Tough nut to crack. Even if I boot the machine as Administrator and am off the network it won't let me delete the SMS directory, or most files in it; nor slay the processes.