VSS Client installation
1. Open VSS in client system.
2. Right click on project source, select “Set working Folder”.
3. Select the client system project folder to set the set working folder for vss to interact with the client to vss.
4. Create new folder(Ex:- Ad-Dashboard)
5. Right click on Project, select “Get Latest Version” to copy the server version of project to client system.
6. Open the project source folder.
7. Double click on Solution, it will open the project in Microsoft visual studio.
(Note:- The arrow symbols indicate that the project in vss).
8. The lock symbols indicate that the project is in vss and no other developer is check out the source.
9. If anybody check the source files, the right arrow symbol will be associated instead of lock symbol and the other developer will know that by a developer symbol is displayed instead of lock. Means that the other developer can view only, no permission to edit.
Rules to use the project which is deployed in vss:-
1. Always open the project with vss, open the vss solution only.
2. Check whether the code is updated, right click on the file which is updated and select “Get latest version(Recursive)”.
3. If you want to modify the source file, right click on the file select “Check out for edit”.
4. Add comment and click on “Check Out”.
5. A right symbol will be displayed instead of lock symbol.
6. And the other person will get the person symbol, indicates that he can’t modify only view it.
7. After code updation, right click on source file which he check out last time and again add comment on what he modified then click on “Check in”.
8. If he doesn’t want to modify the source file which he check out last time, right click on the file select “Undo check out”.
Saturday, August 7, 2010
VSS Server configuration
VSS Server configuration
1. Copy the project into the server (D:\Noah Projects\AD-Dashboard)
2. Open Visual studio 2005.
3. Create a blank solution.
4. Add existing project source to the solution. Right click on solution, select “Existing website”.
5. Now add project to the VSS. Right click on solution, select “Add solution to source control”.
6. Select the vss database then login as admin user.
7. Select the root folder to save the project in to vss.
8. Now the Project has been successfully added to VSS.
1. Copy the project into the server (D:\Noah Projects\AD-Dashboard)
2. Open Visual studio 2005.
3. Create a blank solution.
4. Add existing project source to the solution. Right click on solution, select “Existing website”.
5. Now add project to the VSS. Right click on solution, select “Add solution to source control”.
6. Select the vss database then login as admin user.
7. Select the root folder to save the project in to vss.
8. Now the Project has been successfully added to VSS.
CVS Installation
CVS Installation
1. Run the cvs server in the windows server 2003 32bit system.
2. Select “Complete”
3. After installation select “Start->Programs->CVSNT->CVSNT Control Panel
4. Select “Repository Configuration”
5. Click “Add” to create repository.
6. Select “Standard” as repository to give permissions to repository.
7. Select the repository location in server.
8. Give the name of the repository (\CVS).
9. Select “Server settings”.
10. Select the user administration as per domain.
The CVS server will be configured successfully.
11. After client installation, client need Net beans ide with cvs integration.
12. Open the Net beans, select “Versioning->Checkout” to get the source the
1. Run the cvs server in the windows server 2003 32bit system.
2. Select “Complete”
3. After installation select “Start->Programs->CVSNT->CVSNT Control Panel
4. Select “Repository Configuration”
5. Click “Add” to create repository.
6. Select “Standard” as repository to give permissions to repository.
7. Select the repository location in server.
8. Give the name of the repository (\CVS).
9. Select “Server settings”.
10. Select the user administration as per domain.
The CVS server will be configured successfully.
11. After client installation, client need Net beans ide with cvs integration.
12. Open the Net beans, select “Versioning->Checkout” to get the source the
Exchange Installation Requisites
Installation of Exchange 2007 on Windows Server 2008 64 Bit
Pre-Installation Checklist
Install Windows Server 2008 64 bit version
Configure your static IP address
Activate Auto Updates
Add role - Active Directory Services
Add role - Active Directory Lightweight Services
Add feature - Windows Process Activation Service
Add role - Web Server (IIS)
Add feature - Power Shell
Roles / Features NOT to install
Installing Exchange Server 2007
Allow IGetMail access to your Exchange Server
Adding E-Mail Users
*Note: Please Activate Windows Server with Licensed Key ( Right click on my computer System Properties and Activate)
Pre-Installation Checklist Make sure you have all of the following steps in place before you setup Exchange Server 2007 on Windows Server 2008 64 Bit. For simplicity we are assuming you are setting up a small office where one machine will be used for both the Active Directory and the Exchange Server. This setup works just fine and reduces the number of machines to maintain. If you have a larger office you may want to consider separating the Active Directory machine and the Exchange 2007 Server.
Install Windows Server 2008 64 bit version Exchange 2007 is a 64 bit application and requires 64 bit versions of Windows Server 2003 or Windows Server 2008. You should select a computer that is capable of running the 64 bit version of Windows Server 2003 or 2008. For this example we will start with a clean installation of Windows Server 2008 64 bit version that has not had any roles installed. After installing Windows Server 2008 we set the clock and the name of the server to be "EX2007". At this point this server is configured to be a stand alone computer with default settings.
Pre-Installation Checklist
Install Windows Server 2008 64 bit version
Configure your static IP address
Activate Auto Updates
Add role - Active Directory Services
Add role - Active Directory Lightweight Services
Add feature - Windows Process Activation Service
Add role - Web Server (IIS)
Add feature - Power Shell
Roles / Features NOT to install
Installing Exchange Server 2007
Allow IGetMail access to your Exchange Server
Adding E-Mail Users
*Note: Please Activate Windows Server with Licensed Key ( Right click on my computer System Properties and Activate)
Pre-Installation Checklist Make sure you have all of the following steps in place before you setup Exchange Server 2007 on Windows Server 2008 64 Bit. For simplicity we are assuming you are setting up a small office where one machine will be used for both the Active Directory and the Exchange Server. This setup works just fine and reduces the number of machines to maintain. If you have a larger office you may want to consider separating the Active Directory machine and the Exchange 2007 Server.
Install Windows Server 2008 64 bit version Exchange 2007 is a 64 bit application and requires 64 bit versions of Windows Server 2003 or Windows Server 2008. You should select a computer that is capable of running the 64 bit version of Windows Server 2003 or 2008. For this example we will start with a clean installation of Windows Server 2008 64 bit version that has not had any roles installed. After installing Windows Server 2008 we set the clock and the name of the server to be "EX2007". At this point this server is configured to be a stand alone computer with default settings.
Installation Guide for MOSS2007
Installation Guide for MOSS2007
Hardware requirements
Front-end Web server and application server computers: a dual-processor computer with processor clock speeds of 2.5-gigahertz (GHz) or higher and a minimum of 2 gigabytes (GB) of RAM.
Back-end database server: a dual-processor computer with processor clock speeds of 2.0 GHz or higher and a minimum of 2 GB of RAM.
Software requirements Web and Application Server
Microsoft Windows Server 2003 (Standard, Enterprise, Datacenter, or Web Edition) with Service Pack 1 (SP1)
Microsoft .Net Framework 2.0
Microsoft .Net Framework 3.0
The Web server and application server computers must be configured as Web servers running Microsoft Internet Information Services (IIS) in IIS 6.0 worker process isolation mode.
Each of the computers must be using the NTFS file system. Windows Server 2003 includes a conversion utility (Convert.exe) that you can use to convert an existing file allocation table (FAT) volume to NTFS without losing data.
Back-End Database Server
The back-end database server computer must be running Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with Service Pack 3 (SP3) or later. It is assumed that you have installed and configured the database program on the back-end server computer. You do not need to set up or create specific databases for Office SharePoint Server 2007. The Office SharePoint Server 2007 Setup program will create the necessary databases when you install and configure Office SharePoint Server 2007.
Install Windows .NET Framework 2.0
1. Run .Net Framework 2.0 Setup
Enable ASP.NET 2.0
1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In the IIS Manager tree, click the plus sign ( ) next to the server name, and then click the Web Service Extensions folder.
3. In the details pane, click ASP.NET v2.0.50727, and then click Allow.
Install .Net Framework 3.0
1. Run .Net Framework 3.0 Setup
Install Microsoft Windows Workflow Foundation Runtime. Install and configure 2007 Office SharePoint Server
It is recommended that you install and configure Office SharePoint Server 2007 on all of your front-end servers before you configure Office SharePoint Server 2007 services and create sites. If you want to build a minimal server farm configuration, and incrementally add front-end servers to expand the farm, you can install and configure Office SharePoint Server 2007 on a single front-end server and configure the front-end server as both a Web server and an application server. Regardless how many front-end servers you have in your server farm, you must have SQL Server running on at least one back-end database server before you install Office SharePoint Server 2007 on your front-end servers.
Run 2007 Office SharePoint Server Setup
1. Run Officeserver.exe, on one of your Web server computers.
2. On the Enter your Product Key page, enter your product key and click Continue.
1. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.
4) On the Choose the installation you want page, click Advanced.
5. On the Server Type tab, do one of the following:
If you are setting up a computer that will act as an application server, or a Web server and an application server, click Complete, and then click Install Now.
If you are setting up a computer that will act as a Web server only, click Web Front End, and then click Install Now.
6. When Setup finishes, a dialog box appears telling you that you must complete the configuration of your server. Make sure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.
7. Click Close to start the configuration wizard. Instructions for completing the wizard are provided in the next set of steps.
8) restart the IIS.
****Installation Part is completed****
Go to Program Files-Microsoft office serversharepoint 3.0 central administration
Then Login with authentication
Username:kmipl\administrator
Password: p@sswd@123
Then you will be getting the central administration menu with url :http://km-sharepoint:40882
Click on Application Managementshare point web application management create or extend web applicationcreate a new web applicationcreate or extend web application.-select create a new web applicationin create a new web application ( do not change any fields) then press okselect template -->click ok.-->then go to IIS browse the website and check .
To restore the backup file follow the below procedure:
In command prompt these actions are to be performed:
C:/Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
stsadm -o restore -url http://km-sharepoint:7248/ -filename"D:\Anand\Talk about\talkabout.bak" -overwrite
Hardware requirements
Front-end Web server and application server computers: a dual-processor computer with processor clock speeds of 2.5-gigahertz (GHz) or higher and a minimum of 2 gigabytes (GB) of RAM.
Back-end database server: a dual-processor computer with processor clock speeds of 2.0 GHz or higher and a minimum of 2 GB of RAM.
Software requirements Web and Application Server
Microsoft Windows Server 2003 (Standard, Enterprise, Datacenter, or Web Edition) with Service Pack 1 (SP1)
Microsoft .Net Framework 2.0
Microsoft .Net Framework 3.0
The Web server and application server computers must be configured as Web servers running Microsoft Internet Information Services (IIS) in IIS 6.0 worker process isolation mode.
Each of the computers must be using the NTFS file system. Windows Server 2003 includes a conversion utility (Convert.exe) that you can use to convert an existing file allocation table (FAT) volume to NTFS without losing data.
Back-End Database Server
The back-end database server computer must be running Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with Service Pack 3 (SP3) or later. It is assumed that you have installed and configured the database program on the back-end server computer. You do not need to set up or create specific databases for Office SharePoint Server 2007. The Office SharePoint Server 2007 Setup program will create the necessary databases when you install and configure Office SharePoint Server 2007.
Install Windows .NET Framework 2.0
1. Run .Net Framework 2.0 Setup
Enable ASP.NET 2.0
1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In the IIS Manager tree, click the plus sign ( ) next to the server name, and then click the Web Service Extensions folder.
3. In the details pane, click ASP.NET v2.0.50727, and then click Allow.
Install .Net Framework 3.0
1. Run .Net Framework 3.0 Setup
Install Microsoft Windows Workflow Foundation Runtime. Install and configure 2007 Office SharePoint Server
It is recommended that you install and configure Office SharePoint Server 2007 on all of your front-end servers before you configure Office SharePoint Server 2007 services and create sites. If you want to build a minimal server farm configuration, and incrementally add front-end servers to expand the farm, you can install and configure Office SharePoint Server 2007 on a single front-end server and configure the front-end server as both a Web server and an application server. Regardless how many front-end servers you have in your server farm, you must have SQL Server running on at least one back-end database server before you install Office SharePoint Server 2007 on your front-end servers.
Run 2007 Office SharePoint Server Setup
1. Run Officeserver.exe, on one of your Web server computers.
2. On the Enter your Product Key page, enter your product key and click Continue.
1. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.
4) On the Choose the installation you want page, click Advanced.
5. On the Server Type tab, do one of the following:
If you are setting up a computer that will act as an application server, or a Web server and an application server, click Complete, and then click Install Now.
If you are setting up a computer that will act as a Web server only, click Web Front End, and then click Install Now.
6. When Setup finishes, a dialog box appears telling you that you must complete the configuration of your server. Make sure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.
7. Click Close to start the configuration wizard. Instructions for completing the wizard are provided in the next set of steps.
8) restart the IIS.
****Installation Part is completed****
Go to Program Files-Microsoft office serversharepoint 3.0 central administration
Then Login with authentication
Username:kmipl\administrator
Password: p@sswd@123
Then you will be getting the central administration menu with url :http://km-sharepoint:40882
Click on Application Managementshare point web application management create or extend web applicationcreate a new web applicationcreate or extend web application.-select create a new web applicationin create a new web application ( do not change any fields) then press okselect template -->click ok.-->then go to IIS browse the website and check .
To restore the backup file follow the below procedure:
In command prompt these actions are to be performed:
C:/Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
stsadm -o restore -url http://km-sharepoint:7248/ -filename"D:\Anand\Talk about\talkabout.bak" -overwrite
To Create User in CVS (JAVA)
The below is the cofiguration settings for the CVS user creaton :
Example:
d:\CVSNT --->Enter Key
set cvsroot = :SSPI:localhost:/km-repo
cvs ls
cvs passwd -r cvsuser -a username (as required)
enter password
confirm password
Example:
d:\CVSNT --->Enter Key
set cvsroot = :SSPI:localhost:/km-repo
cvs ls
cvs passwd -r cvsuser -a username (as required)
enter password
confirm password
Friday, August 6, 2010
To enable calender in user system after removing admin Rights in domain
Since there is a local security policy on each computer that allows/disallows setting the system time, you should be able to configure a group policy with the same effect. Below are instructions for how to set local system settings.
Setting system access permissions on Windows XP -
To set permissions on Windows XP:
1. Select Start > Settings > Control Panel.
2. In the Control Panel, open Administrative Tools.
3. In Administrative Tools, open Local Security Policy.
4. In the Local Security Settings window, expand the tree for Local Policies and select User Rights Assignment.
5. Right-click the required user right, and select Properties. The appropriate properties window appears (for example, Change the system time).
6. To add permissions:
a. Click Add User or Group. The software opens the Select Users or Groups window.
b. Specify the user ID that requires this permission.
c. Click OK.
d. Click Apply then OK to save your changes and close the Properties window.
7. When you are finished, restart the machine so that the updates will take effect.
Also, here is a link to MS site on how to edit the registry to allow a user to access the time/calendar - http://support.microsoft.com/kb/300022
Hope that helps a bit.
localsecpolwinxp.gif (13.3 KB)
M
Setting system access permissions on Windows XP -
To set permissions on Windows XP:
1. Select Start > Settings > Control Panel.
2. In the Control Panel, open Administrative Tools.
3. In Administrative Tools, open Local Security Policy.
4. In the Local Security Settings window, expand the tree for Local Policies and select User Rights Assignment.
5. Right-click the required user right, and select Properties. The appropriate properties window appears (for example, Change the system time).
6. To add permissions:
a. Click Add User or Group. The software opens the Select Users or Groups window.
b. Specify the user ID that requires this permission.
c. Click OK.
d. Click Apply then OK to save your changes and close the Properties window.
7. When you are finished, restart the machine so that the updates will take effect.
Also, here is a link to MS site on how to edit the registry to allow a user to access the time/calendar - http://support.microsoft.com/kb/300022
Hope that helps a bit.
localsecpolwinxp.gif (13.3 KB)
M
Subscribe to:
Posts (Atom)