Cassy Blog

Today I tried to change the name of test VPC (Running MOSS2007, thus also the computer name in the network…

So far so good, after a while I discovered that one should also check the user-account of the application pools running in IIS … ok no problem …

The real pain-in-the-ass appeared to be MS SQL Server 2005. Changing the Security Logins was no problem but apparently SQL Server stores the computername within the username. When changing the computername, this is not automatically updated *grmbl*

Still my SharePoint sites weren’t working … I checked the user mappings (double-click on the user login), and it appears that the Sharpoint AdminContent user and Sharepoint_Config user are still pointing to users with the old computer name in it. Even the column of “Default Schema” lists these wrong values…

Ok no worries, I type in the correct values, close the window, re-open it and … tadaaaaaaaa the names are NOT changed
That cannot be normal one might think…

Breath in … breath out … let’s change that “Default schema” name entry …

After hours searching for the schema-name, trying to lookup some information about using the SSMS, I found the location in the Master Database. Querying the sys.sys_objects gave nothing but suddenly a view caught my eye “sys.schemas” where I found the wrong record. But this is where my gut-feeling takes over and says … Cassy don’t mess with the System tables …

Changing computer names … never a good idea apparently … and what about the Microsoft – so high valued – integration skills?