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!

In today’s markets managing quality is crucial. These systems provide companies either with a competitive advantage or in some industries they are a necessity to still be able to provide services or goods. But maintaining a quality management system poses many challenges...


Read more


Interested? Contact us

If you want to use the Microsoft Online Services Single Sign in tool. Check the C:\Program Files\Microsoft Online Services\Sign In\SignIn.exe.config file first!


The tool wouldn't want to authenticate me although my username & password were correct.


Why check the config file?
First of all you need to know where exactly your online service is located.





Do you contact the service using:
https://home.emea.microsoftonline.com/ or https://home.microsoftonline.com/


if you use emea (Europe, the Middle East and Africa) like I do, check the C:\Program Files\Microsoft Online Services\Sign In\SignIn.exe.config. At the bottom of this file there is an endpoint element.


make sure this elements address is referring to the correct url


EMEA users --> https://signinservice.emea.microsoftonline.com/ssoservice and not https://signinservice.microsoftonline.com/ssoservice like in my case.


this small change enabled me to use this tool without any other problem.

Do not try to connect your outlook with the BPOS Exchange server. Outlook supports only 1 exchange account at a time so the other one will be removed. Make sure you export a backup (*.PST) first!

Some things that you need to know before you start developping SilverLight solutions that displays data from SharePoint by using the default webservices.


Asynchronous
Every call to a webservice from Silverlight is asynchronous


crossdomain.xml and clientaccesspolicy.xml
While debugging, your Silverlight application runs on a localhost and hereby it cannot connect to a webservice on another domain. In order to tell silverlight that it has access to these webservices you need to place the crossdomain.xml on the root of the webserver where these webservices exist.


In sharepoint this is a problem, because you cannot simply put them in the root by copy paste in IIS explore mode. You need to use sharepoint designer to connect to the sharepoint server and add the xml file. Afterwards make sure the file is available at this location:
http://server:port/crossdomain.xml

What happens when your server contains a special url like http://server:port/ test/
http://http://server:port/ test/crossdomain.xml, you cannot copy paste this xml file using SharePoint Designer because it won't open http://devmoss:8080!


More info: http://msdn.microsoft.com/en-us/library/cc197955(VS.95).aspx


Create a proxy service!
In order to keep the silverlight application clean, reference your custom webservice. This webservice exposes the data needed in the silverlight application. Make sure that you set the correct impersonation settings in the web.config.

Enable the invoke button remotely on your webservice