wlaidlaw

For reference when BS EN 60309 outlets are installed for "untrained personnel" they should have mechanical interlocks. Ie they can only be made live when the correct plug it mated. This prevents students inserting paperclips etc and getting a shock! Re: plug top RCDs these have a habit of failing closed - in that they no longer function as an RCD. They need to be tested periodically (with a proper RCD tester) and at every use by pressing the test button. Will

Can you try the following from your exchange box: Telnet to the postfix box on port 25 Simulate sending an email by typing the following. helo exchange mail from: [enter valid email address on exchange server] rcpt to: [email protected] data test data . If you post back the output that will help to figure out what is happening. Will

You need to configure posfix to allow relaying of email from your exchange server. In /etc/postfix/main.cf (or similar) Make sure you have lines like: mynetworks = [ip of postfix server, [ip of exchange server as seen by postfix server] relay_domains = Hope this helps. Regards Will

Well I finally have got to the bottom of this... All of my test accounts have "been arround for a while" therefore at some point in the past have connected to printers on servers which no longer exist. These connections have been stored in the registry (as they should). When our existing (old script) touches printers it uses con2prt.exe It appears con2prt.exe does not properly remove a printer which it is unable to connect to, it removes the "visible bits" but leaves connection settings in the registry. If I load the ntuser.dat file into a regedit and remove the old junk then the script progresses as it should. Just for reference, if this problem exists you cannot use the WMI method others suggest - that times out so the array cannot be looped. Hope this helps someone else out in the future! Will

Thanks for all your help. At least I know that the code should work. I think I will do some packet logs tommorrow using ethreal to see if I can find out what happens in that time frame. Will

I have enhaced the code slightly so that it logs every printer found not just the network ones. 'Loop round all printers, only list ones that start \\ Set WSHPrinters = WSHNetwork.EnumPrinterConnections For LOOP_COUNTER = 0 To WSHPrinters.Count - 1 Step 2 If Left(WSHPrinters.Item(LOOP_COUNTER +1),2) = "\\" Then LogMsg("Found Network Printer: "&WSHPrinters.Item(LOOP_COUNTER +1)) Else LogMsg("Found Local Printer: "&WSHPrinters.Item(LOOP_COUNTER +1)) End If Next This gives the following at logon: (printer names replaced by ***) 21/09/2009 15:56:30: Listing all mapped network printers... 21/09/2009 15:56:40: Found Local Printer: *** 21/09/2009 15:56:40: Found Local Printer: *** 21/09/2009 15:56:40: Found Local Printer: *** 21/09/2009 15:56:40: Found Local Printer: *** 21/09/2009 15:56:40: Found Local Printer: *** 21/09/2009 15:56:40: Found Local Printer: *** 21/09/2009 15:56:40: Found Local Printer: *** 21/09/2009 15:56:40: Found Network Printer: \\***\*** 21/09/2009 15:56:40: Found Network Printer: \\***\*** If I run the code after logon there is no delay, or indeed if I run the same code again later on in the script there is no delay. If I put a sleep in the script to say wait 2 mins and then list the printers, this makes no difference the script still sits there for 10 seconds. It looks like it is actually conncting to the server to verify the printers exist. Could this casue the delay?

Hi All, I am writing a new logon script in VB Script. As part of this I need to check the network printers that the user already has connected, and connect/disconnect printers as requires. The following code works very well, however if I run it as a logon script it takes 9/10 seconds to run. If I run it after logon it takes less than a second. As a logon script it seems to spend most of the time doing 'nothing' with a quick burst right at the end. Does anyone have any ideas as to why this is? Or any ideas as to how to get the info in some other way without the delay? 'Loop round all printers, only list ones that start \\ Set WSHPrinters = WSHNetwork.EnumPrinterConnections For LOOP_COUNTER = 0 To WSHPrinters.Count - 1 Step 2 If Left(WSHPrinters.Item(LOOP_COUNTER +1),2) = "\\" Then LogMsg("Found Printer: "&WSHPrinters.Item(LOOP_COUNTER +1)) End If Next Many thanks Will

We use a LES100 circuit from BT to connect to our council/RBC. We don't use anywhere near the full capacity so I can't comment on that. I can say that the latency is very low. 1ms ping times across the link are the norm, and you really can treat it like part of your LAN in that respect. The BT installers did a very neat and professional job. Hope this helps somewhat.

Probably the easiest way to find out is as follows: Prepare another temporary volume, on a (relatively) unused (in terms of access) set of disk(s). Whilst you are seeing the high queue to your E: volume, create a lot of I/O to your temp volume (for example copy a few big files to here). Watch the disk queue on E: - If it starts to rise dramatically, stop your test I/O - your issue is likely to be communication to your physical disks. This could be the FC comms or it could be the controller backplane itself. If the queue stays roughly the same you can pretty much say that the limiting factor is the disk grouping itself. Dependant upon your storage system you may be able to get some good stats from that... Often you need to use the command line to retrieve a csv file. Hope this helps Will

I would break down the Avg Disk Queue counter to be per volume rather than a total of all volumes. This will show you where the queue is forming. You then know where to spend your money! I have converted some RAID5 arrays to RAID1 and RAID10 (dependent on volume size) and the performance increase has been incredible. Don't assume that just because you have good kit (SAS drives for example) you can ignore the limitations of the equipment. Schools can (and do) regularly generate enough traffic to exceed these.

How about a Zoom H4. This records onto SD Cards. ZOOM | H4 | PA, Disco & Musical Equipment | Audio, Video & TV | CPC I would have said the quality was more than sufficient for music exams, and it will take external mics if required. Obviously for a full days session you will need a few SD cards, and need to remember to burn the files to audio CD later.

Where do I start.... Yes it does detect each session on the Terminal Server, and runs a copy of securusn.exe per user. However, in our experience this is where the good news ends. We used to regularly get an error saying the DB was corrupt on the TS, requiring securus to be removed form the TS and re-installed. I would say we used to get at best 3 days between having to re-install. (Don't forget as you need to switch to install mode to do this, so there should be no users on the TS). We also had an issue where a Sophos process was interacting with a Securusn process even after users had logged of. This meant that the user's registry was hung open until the terminal server was rebooted. You would have to do the maths based on your usage pattern, but here that resulted in over 150 profiles being active on a TS at the end of the day! We had to implement nightly reboots then run delprof to remove these hung profiles. To be fair to all companies, this issue may have been down to our config, but no solution was found by any party. The last issue was with securusn processes consuming excessive CPU cycles when the users session became idle. I never got to the bottom of the issue entirely, but it seams that when a thin client blanked the screen (in a screensaver kind of way), the session was marked as idle on the TS. The securusn.exe process running in the context of the user would then use all available cycles on it's processor. In our case 4 processes like this and the whole server stopped as it was at 100%. I don't know why this happened, but technical support never got to the bottom of it before it made our TS system unusable. Like I have said above these are my experiences and may not be representative - just a report of what I saw. If anyone wants any more info, feel free to PM me.

Just to confirm that if decline the update via WSUS the clients do eventually stop offering to install it (took 24/36 hours here). The unattended remove command I posted above will clean the machine for you. So it's not quite as bad as I first thought. Will

To uninstall add the following code to your machine startup script: IF exist c:\WINDOWS\$NtUninstallKB917013$\spuninst\spuninst.exe c:\WINDOWS\$NtUninstallKB917013$\spuninst\spuninst.exe /quiet Note that where I have tested it the machine reboots after uninstall. Unfortunately if you have updates set to install automatically it will be reinstalled again - until you reboot then it will be removed. Until the next time the update is installed ..... argh! Declining the update within WSUS does not effect computers that have already downloaded the update... double argh! Will

The first step has got to be tying the fault down to one of the following 3 categories: *Load on the terminal server. [use perfmon running from a remote PC to monitor CPU usage] *Network load between the Terminal Server & DC. [use network monitoring tools or atleast Network tab in Task Manager on both servers] *Load on the DC [use perfmon running from a remote PC to monitor CPU usage] My guess would be CPU (or possibly disk throghput) on the Terminal server or Network Load. What type of profiles do you use? By any chance are your profiles stored on your DC? I would recomend agaist promoting a TS to a DC - bad move from a Security point a view. Also a lot of badly written apps fail as there is no local machine SAM. Will