How to check which .NET version is currently used?
Environment.Version will always return "version = {2.0.50727.3082}", because Environment.Version returns the CLR version, NET 3.0 and 3.5 are both build upon 2.0 and still use the 2.0 CLR. They basically just add additionall class libraries. That's why Environment.Version and other APIs return 2.0 to you.


How to check if certain .NET version has been installed?
Kadir Sümerkent has written a nice function that works perfectly till .NET version 3.5.
http://www.sumerkent.com/index.php/2009 ... installed/

How to check if .NET 3.5 SP1 has been installed?

 internal static bool IsNET35SP1Installed(){
    string Fx35RegistryKey = @"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5";
    object Fx35ServicePack = Registry.GetValue(Fx35RegistryKey, "SP", null);
    if (Fx35ServicePack == null || (int)Fx35ServicePack < 1)
    {
        return false;
    }
    return true;
}

How to check if Microsoft Chart Controls has been installed?

internal static bool IsAspChartControlsInstalled()
        {
            string location = Environment.GetFolderPath(Environment.SpecialFolder.ProgramFiles) + @"\Microsoft Chart Controls\Assemblies";
            DirectoryInfo chartControlsAssembliesDir = new DirectoryInfo(location);
            if (!chartControlsAssembliesDir.Exists)
            {
                return false;
            }
            else
            {
                if (chartControlsAssembliesDir.GetFiles().Count() < 6)
                {
                    return false;
                }
            }
            return true;
        }

How to check which Culture Info the SQL Server is currently using?
http://tomvangaever.be//blog/comments.p ... 106-122529

Check if current windows server is 2003 R2
http://tomvangaever.be//blog/comments.p ... 404-112005

More to come when we need a new environment check!

Microsoft® Windows® SharePoint® Services 3.0 Service Pack 2 (SP2) and Microsoft® Office SharePoint® Server 2007 Service Pack 2 (SP2) include updates designed to improve performance and availability in your SharePoint server farm, along with fixes to known issues across SharePoint Products and Technologies.

In addition, SP2 provides enhancements designed to support greater interoperability, improve user experience and reduce administrative burden.

Finally, SP2 provides the groundwork for an eventual upgrade to the next major version of SharePoint Products and Technologies.

It’s important to note that the SP2 releases also incorporates previous major updates, including Service Pack 1 (SP1), the Infrastructure Update, and all of the cumulative update packages up to and including those released in February 2009.

More info:
http://blogs.msdn.com/sharepoint/archiv ... s-3-0.aspx

1) Create a back-up of your Outlook (pst file)
2) Connect your outlook to your new BPOS exchange service
3) Restore your previous outlook from the pst file
4) Click send/receive to update the exchange server (this can take a while)


Here you go!

Service Pack 2 for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 due to ship April 28th


http://blogs.technet.com/office_sustain ... -28th.aspx

We created a BASE2008.vhd disk, so when a new server is required we could easily use this base diks to skip the whole installation part and simply rename the server. Everything worked just great. Adding the new server to the domain and the installation of the new SQL server 2008 went as smooth as we suspected.


But when we wanted to add new users and groups to the SQL server we received the same error:
"Windows NT user or group ‘username’ not found. Check the name again."


Because of the "clone" we took, we did change the servername but we never altered the SID of the server. There are 2 possibilities to fix this error:


The newsid tool.
- remove this registry key using this node 'REG DELETE HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wow6432Node /f'
- run the newsid tool and create a new SID for the server
- do not forget the reconnect the server to the domain



The sysprep tool.

- OOTB installed on wind2008, run this on your base2008.vhd (%WINDIR%\System32\Sysprep\sysprep.exe)
- select OOBE and don't forget to check generalize. Press OK
- every time you start a new server from this base. It will be like you just installed it.



So the fix this problem with our SQL server we used the first tool and added the server to the domain again. Afterwards we update our base disk for the next servers...

good luck!