Sunday, 20 May 2012

Database attach method to upgrade to a new farm

ADDCONTENTDB


stsadm -o addcontentdb -url  http://intranet  -databasename wss_content_hr -databaseserver yoursqlservername\instancename

if you have multiple subsites then you can very well include all of those stsadm database attach command in a batch file and execute it at one stretch.
ex:
save the below in a execute.bat file:
'----
stsadm -o addcontentdb -url http://intranet -databasename wss_content_hr -databaseserver yoursqlservername\instancename >> result.txt


stsadm -o addcontentdb -url  http://intranet/sites/hr -databasename wss_content_hr -databaseserver yoursqlservername\instancename >> result.txt


stsadm -o addcontentdb -url  http://intranet/sites/it -databasename wss_content_hr -databaseserver yoursqlservername\instancename >> result.txt

'----
the above file execute.bat once executed will append result.txt with the upgrade status.

dealing with user password credential manager


i .   login with the current user account.
ii.   Click Start and type run in the search and hit Enter .

iii.    type "control userpasswords2 " in the run window and hit Enter

iv.    check if the check box which says Users must enter a user name and password to use is checked. If the check box is checked then uncheck the check box, click on apply and ok tab and hit enter.

v.    Restart the system.
vi.    You will be able to see different users in the logon screen.

 delete stored passwords from your machine..(win 7)

     click Manage Password

if you are not sure which application is using your credential please feel free to remove it. :)

exciting office web apps for SharePoint 2010

No need of office installation on client machines, instead integrate web app bunch with Sharepoint 2010.
saves client licensing (CALs) cost or for those who needs to extend the office feature on the web browser. Clients can open office documents from anywhere outside office network like from Airport or from public internet zone using authorized connection. For better performance install Silverlight on client computers.
installation reference:

How to change SQL Server Name or Instance Name

applies to all SQL ver including Denali.
i. Open SQL Server Management Studio and click New Query.
ii. Type Select @@ServerName to verify that the server name. In this example, Windows 2003 from WIN2K3R2EE to SQL Server is used. If windows hostname is changed doesn't mean that SQL Server 2005 name will be automatically changed. It will still return the old name. Let's fix it.
3. Next, type sp_dropserver 'WIN2K3R2EE'
4. You are now ready to add the correct name by typing sp_addserver 'SQLSERVER'. local
at this point if you need to change instance name, execute the below query:
sp_dropserver 'Server Name\old_Instance_name'
go 
sp_addserver 'ServerName\New Instance Name','local'
go


5. Restart sql server and the sql server agent by opening a command prompt and typing net stop mssqlserver and net start msssqlserver. To stop and start the sql server agent, type net stop or start sqlserveragent.
6. Click New Query in SQL Server Management Studio and type select @@servername to verify everything is correct and you have successfully changed the sql server name.

high availability moss 2007 development and production environment

I attained the below infrastructure from scratch (a mix of windows 2003 R2 Ent 32bit and 64bit) for our team during mid of 2010
2 Tier MOSS 2007 network diagram
2 Tier MOSS2007 Architecture for both development and production environment

Saturday, 19 May 2012

hide special user accounts from windows 7 display screen

How to Create Hidden User Account (Hide User Account from Welcome Screen) in Windows

Windows operating system including Windows7, Windows Vista and Windows XP allows multiple user accounts to be created on the computer, be it administrators or standard users. When there is more than one user accounts been defined and created on the PC, Windows will display Welcome Screen, with all available user accounts listed so that user can click and login.

However, showing and displaying of user accounts on the Welcome Screen is probably a weakness in the security point of view, more so if the user account is intended to be a hidden or backup user account. In fact, there is trick to make user account or administrator account that normally been listed on the Welcome Screen to be hidden from view.

In order to hide a user account (which also means create a hidden user account) in Windows XP, Vista, or Windows 7, just go to Control Panel User module and create an additional user as usually do (Control Panel -> User Accounts and Family Safety -> User Accounts in Windows 7 and Windows Vista). If you already have an existing user that wants to be made hidden, invisible or disappeared from Welcome Screen, then go straight to guide below.


1. Run Registry Editor (RegEdit.exe).
2. Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon \SpecialAccounts\UserList



Note: If SpecialAccounts and UserList is not found, create new sub-key and name them accordingly.

3. Select UserList, and in the right pane, right click any blank space, and point to New -> DWORD (32-bit) Value.

4. Name the new DWORD registry value name as the exact same name that match the name of the user account to be hidden.


For example, if the user ID of the user account is John, the name the registry value as John.
5. Double click on DWORD registry value, and set the value data to 0 in oder to hide the account from Welcome Screen.



Tip: To display the user account on Welcome Screen again so that it's visible again, delete the
registry entry, or set the value data to 1.

6. Exit Registry Editor.
7. Log off or restart computer to make the change effective.



Tip: In order to login into Windows using an user account that has made hidden and invisible, just press Ctrl+Alt+Del to bring up Windows Logon dialog, and then type in the user name and password manually.

SQL 2008 R2 'Cluster Name' registration failure .. event ID 1196 and Event ID 1119

this is important for setting up SQL 2008 fail-over cluster.
Check evenlog for the event id 1196 or 1119. 

cause : 
while creating static record the option "allow any authenticated user to update DNS records with the same owner" was not selected. So, cluster nodes (active node) who will own the cluster name resource won't be able to register this resource record to the DNS database.  

Solution:
Go to DNS, find the record ( A & Pointer record) for the cluster name resource.





-right click
-go to properties
-select security make sure the "Authenticated users" are included
-make sure it has "Write: rights and Special permissions
-click Advance, locate authenticated users, and click edit
-make sure, Write all properties, Read permissions, All Validated Writes are selected
-click okay three times to exit