Hexagon v3: Part 5 – Over clocking

This is a post about my new custom build PC. To see all posts, check out Hexagon v3: Part 1 – Main Components

 

Since Hexagon v3 is now working (Vista SP2 with all updates), it’s time to get started with over clocking. After all, this is just the process of using components outside their specification to save some money ;-).

As I said in a block post before, I want to over clock the CPU only. Therefore, I’m  concentrate on torturing and monitoring the CPU.

For torturing, I use a special program by Matthias Withopf: Core2MaxPerf (bottom of the page). This is the only program I know that is really able to fully load a Core CPU (yes, even Prime95 isn’t able to do so). For temperature monitoring I will use another tool from Mr. Withopf: CPUTempWatch together with SpeedFan by Alfredo Milani Comparetti.

In case you are wondering why I use these two instead of Gigabytes’s EasyTune6: The “CPU Temperature” inside the BIOS and EasyTune6 is measured on the board and has nothing to do with the real temperature of your CPU. On the other hand, I know there are several other programs that claim to read the real temperature from the CPU directly. Well, here’s an example what you get (example from my old computer):

Do you find the error on this picture? If so: That’s the reason why I trust only SpeedFan and CPUTempWatch.

As I started testing with Core2MaxPerf and Prime95 (with all values AUTO, no over clocking), the somewhat expected happened: The system crashed. After some testing with various BIOS settings, it turned out that the memory modules were failing.

If the memory is configured to anything else than X.M.P. Memory (800 MHz/ 1600 MHz) with 1.65V voltage and the default timings (All values set to [AUTO] = 8-8-8-24), the system crashes. After that change, the system was stable.

Note: Actually I was running this for over an hour, but the print screen didn’t copied anything so I simply started Core2MaxPerf again and took the screenshot.

An 8 hours Prime95 stress test in Blend and In-place large FFT mode also worked, so I knew the system was stable and could start over clocking.

 

Given the crashes because of the memory modules, it was clear that the memory needs to be configured exactly as before or I would face crashes again. My initial goal was just above 3.0 GHz, so the base clock should be 151 MHz. However, this would cause the memory run outside the specification. Therefore, I created this small excel sheet to do the math:

I ended up using 160 MHz as the back clock, x10 as the memory multiplier and x20 as the Uncore multiplier. This means that both the memory and the Uncore frequency are exactly the same as before and no bad things should happen there. I also raised the CPU vCore slightly to 1,275V and the QPI Voltage to 1,280V (to make sure it’s within a 0,5V range of the memory modules voltage).

Now I simply repeated all tests:

The temperature climbed to 73°C, which is okay for me (the CPU will shut down at 100°C) but the CPU fan management of the board is not as good as it could be.

If you use EasyTune6 and change the temperature control, the temperature is degreased to 69°C. That’s because the CPU cooler is than running at 1300 RPM while before it was only running at 800 RPM.

However, this would require having EasyTune6 running all the time and I don’t want that. Maybe I will later on try to control the CPU fan with SpeedFan to have more control over it.

The final test, Prime95 Blend for over 9 hours, worked as well:

Just for your reference: Although Prime95 was now running on all cores for more than 9 hours, the temperature wasn’t as high as with Core2MaxPerf. That’s what I meant with “Full Load Testing can only be done with Core2MaxPerf”.

 

Well, that’s it - I’m done with the setup of Hexagon v3. If just Windows 7 would be available already…

Hexagon v3: Part 4 – Full Assembly

This is a post about my new custom build PC. To see all posts, check out Hexagon v3: Part 1 – Main Components

 

The remaining assembly should be a peace of cake if you have at least build one PC in your life.

Install the CPU on the motherboard (this is described very good in the manual of the main board  and then install the Kabuto onto it. Using push pins with a cooler of this size can be tricky, but after watching the Kabuto installation video at Eiskaltmacher.de, this was a snap. You only need to make sure that the ends of the heat pipes are facing upwards!

When installing the memory modules, I did it (of course) wrong the first time. To enable triple channel operation, the modules must be installed into the white slots. Not the blue ones, although the memory modules are blue also.

When installing the hard disks, I noted each serial number of each drive and the SATA port it is connected to. Given how many screws you need to remove until you can exchange one, I though this would help in case of a hard disk failure.

I tried my best to do the cabling right this time, but the result is still somewhat… ugly.

   

Anyway, the good news is: It came to life! So I simply installed Vista and did the typical Windows Update stuff.

Since this is the first time I’m using Samsung HDs (I mostly used Hitachi drives before), I went on to change the Automatic Acoustic Management (AAM). Hitachi usually delivery their drives set to Middle, so the drive is not operating at full speed in favor for more silence. Therefore I decided to set the Samsung HDs to Fast.

This can only be changed with ES Tool from DOS. Therefore, I downloaded “Driver Free Disk for BIOS Flashing” from Bootdisk.com, copied ES Tool onto the floppy and booted.

Important: ES Tool can only access the HDs when the Intel ICH is no responsible for the disk. In other words: When the drives are set to IDE and not configured as array. Even if a an array is already configured, you can always change the setting “ICH SATA Control Mode” to IDE and “SATA Port 0-3 Native Mode” to DISABLED, make the changes with ES Tool, and change it back again. The array will not be destroyed as long as you do not write any data on the disks.

Using ES Tool is simple: When you see the DOS prompt, type ESTOOL to start it. I will then display all drives it has found. Select the first, select “AAM Mode” from the menu, change the value to FAST and select PROCESS. That’s it. To select another drive, simply select AUTO DETECT and repeat.

By default, all HDs had AAM set to DISABLED and the actually results of this change where by far not as good as I hoped.

Here are the benchmarks before the change (AAM = DISABLED):

 

And here after the change (AAM = FAST):

 

Once the access time was significantly improved, same values were even worse than before. As it seems, AAM set to DISABLED is nearly the same as FAST when using Samsung drives.

Media Player Classic Rollout

We just solved a problem a customer had with media playback using Windows Media Player (WMP).

Basically there were two problems associated with WMP: First, several users complained that opening a file with WMP takes a long time. Secondly, a lot of users were confused by all the controls WMP offers and asked how to “clean” the interface. The help desk database showed that about 130 tickets were created about these issues in the last three months.

Our first idea was to see if we could solve this problem with registry settings and/or GPO settings. However, I personally didn’t use WMP for several years now; I always use Media Player Classic (MPC). Showing Media Player Classic the users that reported one of these issues the most resulted in one reaction: “Great. Exactly what I need”. If you do not quite understand what the user means, here’s an example of the interface difference between WMP and MPC:


_


Sure thing, this means we will roll out MPC to 550+ computers! A very important requirement of this rollout was that the changes could be reverted back easily. As Microsoft is constantly updating WMP, it might happen that a new version brings back a “clean” interface and is faster. At that time, MPC would be replaced by WMP again.

Therefore, we have created some .REG files and some .BAT files that install MPC. These scripts will then be executed by the computer management solution of the customer.

The first thing is to download MPC from http://mpc-hc.sourceforge.net/, and copying these files to Program Files folder.

md "%programfiles%\Media Player Classic\"

copy S:\soft\MPC\MPC_prog\*.* "%programfiles%\Media Player Classic" /V /Y

After that, Windows should know that a new program is available so we’ll add MPC to the “Applications” list by using this .REG file (simply import this file with the command regedit.exe /S app.reg)

REGEDIT4

[HKEY_CLASSES_ROOT\Applications\mplayerc.exe]
@="Media Player Classic"
"FriendlyAppName"="Media Player Classic"

[HKEY_CLASSES_ROOT\Applications\mplayerc.exe\DefaultIcon]
@="mplayerc.exe,0"

[HKEY_CLASSES_ROOT\Applications\mplayerc.exe\shell]
@="open"

[HKEY_CLASSES_ROOT\Applications\mplayerc.exe\shell\open]
@="&Open"

[HKEY_CLASSES_ROOT\Applications\mplayerc.exe\shell\open\command]
@="mplayerc.exe \"%L\""

[HKEY_CLASSES_ROOT\Applications\mplayerc.exe\shell\play]
@="&Play"

[HKEY_CLASSES_ROOT\Applications\mplayerc.exe\shell\play\command]
@="mplayerc.exe \"%L\""

[HKEY_CLASSES_ROOT\Applications\mplayerc.exe\SupportedTypes]
"WAV"=""
"WMA"=""
"MP3"=""
"OGG"=""
"SND"=""
"AU"=""
"AIF"=""
"AIFC"=""
"AIFF"=""
"MIDI"=""
"MPEG"=""
"MPG"=""
"MP2"=""
"VOB"=""
"AC3"=""
"DTS"=""
"ASX"=""
"M3U"=""
"PLS"=""
"WAX"=""
"ASF"=""
"WM"=""
"WMA"=""
"WMV"=""
"AVI"=""
"CDA"=""
"JPEG"=""
"JPG"=""
"GIF"=""
"PNG"=""
"BMP"=""
"D2V"=""
"MP4"=""
"SWF"=""
"MOV"=""
"QT"=""
"FLV"=""

After this, users can already right click any supported file type, select “Open with..” and choose “Media Player Classic”. However, when doing so this won’t work because Windows does not know where the file “mplayerc.exe” is. This REG file will help Windows to locate it:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\mplayerc.exe]
@="C:\\Program Files\\Media Player Classic\\mplayerc.exe"
"Path"="C:\\Program Files\\Media Player Classic\\"

Although it is of course possible to include the complete path in the first REG, we are using the AppPaths here because this gives us one location where MPLAYERC.exe is located. This will be more important later on.

The next step is to associate the needed files with MPC. As said earlier, we are trying to accomplish this as least changes as possible. Therefore we are simply adding to each file type that should open with MPC, a new command “Play2” and make this command the default. That way, switching back to Windows Media Player just requires changing the default command.

Please note that we are only changing those files that customer is using (often or sometimes) and leaving all other, even if MPC supports them, alone:

REGEDIT4

; .wav = soundrec (#1)
; default "play"
[HKEY_CLASSES_ROOT\SoundRec\shell]
@="play2"

[HKEY_CLASSES_ROOT\SoundRec\shell\play2]
@="&Open"

[HKEY_CLASSES_ROOT\SoundRec\shell\play2\command]
@="mplayerc.exe \"%L\""

; .mpeg = mpegfile (#2)
; default "play"
[HKEY_CLASSES_ROOT\mpegfile\shell]
@="play2"

[HKEY_CLASSES_ROOT\mpegfile\shell\play2]
@="&Open"

[HKEY_CLASSES_ROOT\mpegfile\shell\play2\command]
@="mplayerc.exe \"%L\""

; .avi = avifile (#3)
; default "play"
[HKEY_CLASSES_ROOT\avifile\shell]
@="play2"

[HKEY_CLASSES_ROOT\avifile\shell\play2]
@="&Open"

[HKEY_CLASSES_ROOT\avifile\shell\play2\command]
@="mplayerc.exe \"%L\""

; .mp3 = mp3file (#4)
; default "play"
[HKEY_CLASSES_ROOT\mp3file\shell]
@="play2"

[HKEY_CLASSES_ROOT\mp3file\shell\play2]
@="&Open"

[HKEY_CLASSES_ROOT\mp3file\shell\play2\command]
@="mplayerc.exe \"%L\""

; .mid = midfile (#5)
; default "play"
[HKEY_CLASSES_ROOT\midfile\shell]
@="play2"

[HKEY_CLASSES_ROOT\midfile\shell\play2]
@="&Open"

[HKEY_CLASSES_ROOT\midfile\shell\play2\command]
@="mplayerc.exe \"%L\""

; .MKV -> Not existsting by default (#6)
[HKEY_CLASSES_ROOT\.mkv]
@="MKVFile"

[HKEY_CLASSES_ROOT\MKVFile\DefaultIcon]
@="mplayerc.exe,0"

[HKEY_CLASSES_ROOT\MKVFile\shell]
@="play2"

[HKEY_CLASSES_ROOT\MKVFile\shell\play2]
@="&Open"

[HKEY_CLASSES_ROOT\MKVFile\shell\play2\command]
@="mplayerc.exe \"%L\""

; .divx = divxFile (#7)
; default "open"
[HKEY_CLASSES_ROOT\divxFile\shell]
@="play2"

[HKEY_CLASSES_ROOT\divxFile\shell\play2]
@="&Open"

[HKEY_CLASSES_ROOT\divxFile\shell\play2\command]
@="mplayerc.exe \"%L\""

; .FLV -> Not existing by default (#8)
[HKEY_CLASSES_ROOT\.flv]
@="Flash.VideoFile"

[HKEY_CLASSES_ROOT\Flash.VideoFile\DefaultIcon]
@="mplayerc.exe,0"

[HKEY_CLASSES_ROOT\Flash.VideoFile\shell]
@="play2"

[HKEY_CLASSES_ROOT\Flash.VideoFile\shell\play2]
@="&Open"

[HKEY_CLASSES_ROOT\Flash.VideoFile\shell\play2\command]
@="mplayerc.exe \"%L\""

As you can see, we are reusing the AppPath from above by executing “mplayerc.exe” without any path. If you want to install MPC in a different folder, just change the AppPath and everything else will still work. We simply find that a simpler solution then entering the complete path in every command, although Windows needs some milliseconds more to locate mplayerc.exe.

Once all these REG files have been imported (REGEDIT.EXE /S (SOMETHING).reg), give it a try if all files are opened with MPC as expected. In case you need test files, some very good ones could be found at Fx Sound and Magic.

Enjoy!

Hexagon v3: Part 3 – Case Assembly

This is a post about my new custom build PC. To see all posts, check out Hexagon v3: Part 1 – Main Components 

 

Finally, all parts for Hexagon v3 have arrived. Time to get this rolling.

Starting with the assembly, I first installed the standoffs for the motherboard into the case. While it’s empty, this is very easy to do. I used all available screw holes of the EX58-UD5, so at the end I installed nine standoffs.

Next was to completely disassembled the Twelve Hundred. As I said, I want to exchange all fans it has with the SilentWings ones.

I started with the two case fans at the back. It’s a complete no brainer, you only need to remember to push out the two speed  switches from the back of the case.

A little bit more work is needed for the three drive bays. The problem is that the SilentWings use push pins and require a slightly bigger hole than the screws Antec uses. Left is the picture of the fan holder as delivered, on the right after the rework.

 

I only changed three holes, because one isn’t usable (speed controller knob) but three will keep the fan in place also. Once finished, I had four fan holders, three of them are for the front of the drive bays, one for the back (extra CPU cooling). Oh, and I also have five Antec TriCool spare fans now :-).

Assembling the drive bays again isn’t quite a problem. However, due to the size of the push pins the air filter needs some force to be installed again.

After that, I temporary installed the main board to get an idea how the cabling should be. Given that both the DVD drive and the floppy are installed with those ugly, old, wide and non flexible cables, I decided to install them at the bottom. That way, the cable aren’t going through the entire case.

Getting the floppy drive installed was the hardest part of the entire assembly. I spent nearly an hour to get it done right. To me, it looks like nobody at Antec has ever used that floppy spare. I ended up securing the adapter, as it chipped out somehow all the time, with the extra cover I installed for the power LED.

So the complete assignment of the bays is as follows (from the top):

• 1-3: One drive bay with two HDs
• 4-6: One drive bay with extra fan on the back (no HDs)
• 7-9: One drive bay with two HDs
• 10: extra cover with power LED
• 11: Floppy
• 12: DVD

Hexagon v3: Part 2 – Case fans

This is a post about my new custom build PC. To see all posts, check out Hexagon v3: Part 1 – Main Components

 

When it comes to cooling, there are two characteristics that are mutually excluded. You want to fans to be silent, means you don’t hear them. On the other hand, your computer wants as much fresh air as it can get which means the fan should run at full power. And this causes noise.

The problem is based how fans work: An engine will spin a propeller that will blow fresh air to the area you need it. The higher the need of fresh air (air flow, measured in CFM – cubic feet per minute), the faster the propeller needs to spin. And this will simply cause more noise. An example might help:

A Silent Eagle SE 120mm (which is designed to be silent) run at 12 volts will spin at 1250 RPM (rounds per minute) and has a loudness of 1,1 Sone. This means: It has a loudness of “very calm talking”. You can hear it, but it’s not disturbing. The air flow of it is in this case 26 CFM.

If you now slow this fan down to 9 volts, it will spin with only 750 RPM and its loudness will go below 0.1 Sone. This means: It has a loudness of “calm breathing”, equals “You just can’t hear it” equals “Silence”. However, the air flow is reduced to 19 CFM.

To have the same air flow (CFM) as before, you would need two fans (38 CFM in total), but still completely silent.

To have a good air flow but also a silent operation, you should go for a fan that is running at low RPMs. To balance the reduced air flow, simply add more fans.

(I should add that an even better solution is to use a bigger fan, for example replacing a 120mm with a 200mm model. However, given how cases are build today, this isn’t an option. If the case expects a 120mm fan, you just can’t install a 200mm fan.)

 

That was also the reason why I choose the Antec Twelve Hundred as my case: It has three 120mm fans in front, two 120mm at the back and one 200mm fan on the top. The only problem with the fans that Antec delivers: You can only switch them between Low, Medium and High. Even when set to “Low”, the 120mm fans are running with 1200 rpm which is far too much for me. The 200mm fan on top of the case runs at “Low” 400 rpm (82 CFM) so this should not be a problem.

I know currently of exactly two fans that have a good airflow together with a silent operation:

be quiet! SilentWings USC 120mm (My number one choice)

Comes with 3-pin connector (not 4-pin for PMW!), 7V adapter to 4-pin Molex (7 volt, 900 RPM) and a 12V adapter to 4-pin Molex (12 volt, 1500 RPM). The fan case is decoupled, so vibrations will not cause more noise.

Sharkoon Silent Eagle SE

Comes with several adapter cables :  "Standard": 4-pin to 4-pin PWM (color: white), "Low Noise" (black): 4-pin to 4-pin Molex 12V (1250 RPM), "Silent" (red): 4-pin to 4-pin Molex 9V (750 RPM) and "Ultra Silent" (blue): 4-pin to 4-pin Molex 7V (300 RPM).

I choose the SilentWings over the Silent Eagle SE for a simple reason: When run in silent mode (7V for the SilentWings, 9V for the Silent Eagle SE), the SilentWings is running at 900 RPM while the Silent Eagle SE is running at 750 RPM. This means that the SilentWings has a better air flow with more CFM.

 One more thing: When installing a fan, always make sure the install it in the right direction. Yes, I know this must sound odd but I also installed a fan in the wrong direction once. Simply have a look at the fan you want to install and check the arrows every fan has (click the picture to enlarge it).

This SilentWings has two arrows: The arrow on the left points to left and indicates that this is the direction the propeller is moving (in this case, to the left). The right arrow shows you in which direction the airflow is. In this case, the airflow will be bottom up, this means the fan will accelerate the air from the bottom to to the top.

ServicePrincipalNameCheck.cs – Check your SPN

In case you are programming with Windows Communication Foundation (WCF), you might want to use Kerberos authentication (instead of NTLM) one day. An example of an WCF client and server that use this security mode can be found on MSDN.

Kerberos authentication is faster than NTLM and more secure. The bad thing is, in order Kerberos is able to authenticate, it will need a ticket and for that it needs a service principal name (SPN) inside Active Directory.

I don’t want to explain all the details about SPNs, since other people already have done this already: 3 Simple Rules to Kerberos Authentication/Delegation SPNs and Using WCF service in load balanced environment with Kerberos delegation.

However, since I just finished the third projects were missing SPNs have caused a, well, not-as-planned, project start, I have created a class that can check SPNs.

The idea behind is quite simple: When the server starts, it will use this class to check if all necessary SPNs are set. If not, the class will return FALSE and you can use the Log property to log an error. That way, the admin is aware that there is a problem.

Please note that this class is intent for self-hosting services. This means, it will check if a SPN of SERVICENAME/HOSTNAME:PORT exists, e.g. CalcService/SERVER01:45563. If you plan to use it from IIS hosted services as well, you need to change this.

Anyway, here we go:

using System;
using System.Collections.Specialized;
using System.Collections.Generic;
using System.Text;
using System.DirectoryServices;
using System.DirectoryServices.ActiveDirectory;
using System.Net;

namespace PleaseChangeMeIDoNotLikeMe

{
    /*
     * This class is intent to check the SPN (Service principal Names) inside a domain environment.
     *
     * You need a SPN as soon as your client wants to use Kerberos authentication, for example: http://msdn.microsoft.com/en-us/library/ms735117.aspx
     *
     * Create this class with the service name you want to use and the port, e.g. “MyService” and 8081.  After that, call the function Check();
     *
     *
     * Given that the current computer name is “DaServer”, this class will search if a SPN of "MyService/DaServer" and
     * "MyService/DaServer.yourdnsdomain.ext" exists.
     *
     * If either of these two does not exist, Check will result FALSE. If more than one exists, it will also return FALSE.
     *
     * Please note: SPN are NOT case sensitive when used in Windows only environments, but are case sensitive when using with UNIX clients.
     *
     *
     * More information about SPN can be found here: http://technet.microsoft.com/en-us/library/cc731241%28WS.10%29.aspx
     *    
     */

    //Copyright (C) 2009 Xteq Systems - http://www.xteq.com/
    //Copyright (C) 2009 TeX Hex - http://www.texhex.info - http://texhex.blogspot.com/
    public sealed class ServicePrincipalNameCheck
    {
        string _service = string.Empty;
        int _port = 0;

        StringBuilder _log = new StringBuilder();

        StringCollection _adsPaths = new StringCollection();
        StringCollection _spns = new StringCollection();

        public ServicePrincipalNameCheck(string ServiceName, int Port)
        {
            if (string.IsNullOrEmpty(ServiceName))
            {
                throw new ArgumentException("ServiceName must be filled");
            }
            _service = ServiceName;

            if (Port <= 0)
            {
                throw new ArgumentException("Port must not be zero");
            }
            _port = Port;
        }

        public string Log
        {
            get
            {
                return _log.ToString();
            }
        }

        public bool Check()
        {
            _log = new StringBuilder();
            _adsPaths.Clear();
            _spns.Clear();

            string computerName = System.Environment.MachineName;
            string fqdn = Dns.GetHostEntry(computerName).HostName;

            _log.AppendLine(string.Format("Computer NetBIOS name: {0}", computerName));
            _log.AppendLine(string.Format("Computer FQDN: {0}", fqdn));
            _log.AppendLine();

            bool bCheckResult1=CheckInternal(computerName);
            bool bCheckResult2 = CheckInternal(fqdn);

            bool bCheckHostCount = true;

            //Write out found AD objects
            _log.AppendLine("Found computer(s):");
            if (_adsPaths.Count > 0)
            {
                foreach (string sHost in _adsPaths)
                {
                    _log.AppendLine(sHost);
                }
            }
            else
            {
                _log.AppendLine("(none)");
            }
            _log.AppendLine();

            //Check if we have more than one entry in _adsPath. If so, several hosts have registered our SPN
            //which is normally not that good idea
            if (_adsPaths.Count > 1)
            {
                _log.AppendLine("Error: More than one AD host was found!");
                bCheckHostCount = false;
            }

            //Write out found SPN
            _log.AppendLine("Found SPN(s) (might include other SPNs as well)");
            if (_spns.Count > 0)
            {
                foreach (string sSPN in _spns)
                {
                    _log.AppendLine(sSPN);
                }
            }
            else
            {
                _log.AppendLine("(none)");
            }
            return bCheckResult1 && bCheckResult2 && bCheckHostCount;
        }

        private bool CheckInternal(string Computer)
        {
            string serviceName = string.Format("{0}/{1}:{2}", _service, Computer, _port);

            _log.AppendLine("Checking for SPN: " + serviceName);

            bool bResult = false;

            string filter = string.Format("(serviceprincipalname={0})", serviceName);

            using (Domain localDomain = Domain.GetCurrentDomain())
            {
                using (DirectorySearcher search = new DirectorySearcher(localDomain.GetDirectoryEntry()))
                {
                    search.Filter = filter;
                    search.SearchScope = SearchScope.Subtree;

                    SearchResultCollection resultColl = search.FindAll();

                    if (resultColl.Count <= 0)
                    {
                        _log.AppendLine("Error: No SPN found!");
                        bResult = false;
                    }
                    else
                    {
                        if (resultColl.Count > 1)
                        {
                            _log.AppendLine("Error: More than one matching SPN found!");
                            bResult = false;
                        }
                        else
                        {
                            _log.AppendLine("SPN check okay");
                            bResult = true;
                        }

                        ProcessResults(resultColl);
                    }

                    _log.AppendLine();
                    return bResult;                   
                }
            }

        }

        void ProcessResults(SearchResultCollection resultColl)
        {
            ResultPropertyValueCollection rpvc;

            foreach (SearchResult res in resultColl)
            {
                rpvc = res.Properties["adsPath"];
                SaveResults(rpvc, _adsPaths);

                rpvc = res.Properties["serviceprincipalname"];
                SaveResults(rpvc, _spns);
            }

        }

        private void SaveResults(ResultPropertyValueCollection rpvc, StringCollection sColl)
        {
            foreach (Object propValue in rpvc)
            {
                string s=propValue.ToString();
                if (sColl.Contains(s) == false)
                {
                    sColl.Add(s);
                }
            }
        }

    }
}