Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1. I chose to take advantage of testing the new version of SharePoint by testing in the same time
the Windows 2008 Server R2 OS because Microsoft provides presently an 180 days evaluation
version of it.
Therefore, I have chosen to create the Virtual Machine with VMware because it is to date the
only way of making run an 64 bit OS guest on a 32 bits OS host.
you can actually create a Virtual Machine running Windows 2008 Server R2 64 bits on a 32 bits
host by using the free version of VMware:
http://downloads.vmware.com/d/info/desktop_downloads/vmware_player/3_0
As usual I will do my best to supply a step by step tutorial as detailed as possible which demonstrates
how to install 2010 SharePoint on Windows server 2008 R2.
- Environment for this SharePoint 2010 installation:
The environment I propose to mount in this tutorial is a development environment that uses a SharePoint
Server 2010 Farm installation on a single computer using several local service accounts in order to
be compliant with the least privilege administration policy.
The SharePoint 2010 content databases will run on a SQLServer 2008 Standard Edition Database
Engine.
2 Creating the Virtual Machine
2.1 Download Windows Server 2008 R2 Evaluation
Windows Server 2008 R2 is available in 64-bit (x64) only.
The Wizard summarize your settings but you can still change some by clicking "Customize Hardware...".
Especially the RAM allocated to the Virtual Machine.
When you click "Finish", the installation begins by loading the files.
Then, click
Troubleshoot tab
Change Settings button
You will access to the "Display Adapter Troubleshooter" dialog.
Set the cursor to the Full position.
Do not look for any product key, as said before, you do not need any, just click next.
The activation will be done automatically through Internet. You will notice then the activation number and
the number of days remaining on the bottom right corner of the desktop.
3.3 Changing Computer Name
Now, click the "Provide computer name and domain" link,then set your new Virtual machine name.
G
4 Configuring the server - Configuration Operations for SharePoint (MOSS
2007 or SharePoint 2010)
4.1 Adding Server Roles and Roles Services - Application Server - Web Server
On the Initial configuration task windows, click "Add Roles"
The "Add Roles" Wizard is opening.
Check the check box for Application Server.
The wizard opens a modal dialog for the Required Features
Then click "Install" and the Roles and Features are being installed
Check the "Installation Result" dialog and close it.
Integrating Reporting Services 2008 with SharePoint 2007 Step 1 - SQL Server 2008
Installation
The next section will detail the required things to do in order to be compliant with these requirements.
7 If you have the SharePoint 2010 Beta version installed on this machine
If you have the previous SharePoint 2010 Beta version installed on this machine, uninstall it and uninstall
also the Microsoft "Geneva" Framework,
As precised by Micorsoft :
"If you have Microsoft "Geneva" Framework installed, you must uninstall it before you install the Windows
Identity Foundation (WIF)."7 Configuring the server - Configuration Operations for SharePoint 2010
8 Installing the manual Prerequistes Softawre
8.1 Downloading and installing SQL Server 2008 SP1
First, we have to update the previously installed SQL Server with the SP1 downlodable at :
SQL Server 2008 Service Pack 1
Do not forget to choose the x64 package
8.2 Downloading and installing Cumulative update package 2 for SQL Server 2008
Service Pack 1
Then, we have to install the Cumulative Update package 2 for SQL Server 2008 Service Pack 1. We also
could install a later Cummulative Update, except the 3 as Microsoft precises it :
"We do not recommend that you use CU3 or CU4, but instead CU2, CU5, or a later CU than CU5."
Cumulative update package 2 for SQL Server 2008 Service Pack 1
Follow the regsitration process. You will be provided an auto extractable package that needs a password
and the appropriate password.
Here is the screenshot after all the process
8.4 QFE for Sharepoint issues - Perf Counter fix & User Impersonation - KB979917
This is a hotfix for 2 Asp .Net issues :
Issue 1
You deploy some partially trusted Web parts on the SharePoint site. These Web parts have more
permissions than they should have. This issue may create a security risk on the SharePoint site. For
example, these Web parts may generate database requests or HTTP requests unexpectedly. This
behavior creates a security risk.
Note:
Partially trusted Web parts are Web parts that are deployed to the Bin directory of a Web application.
Issue 2
The "Requests Queued" performance counter in an ASP.NET performance object functions incorrectly.
When you run the SharePoint site, this issue may decrease the performance of the SharePoint site.
I read the following in the Hotfix documentation, so I wonder if we have to really install it or test
SharePoint behavior first.
"A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem
that is described in this article. Apply it only to systems that are experiencing this specific problem. This
hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we
recommend that you wait for the next service pack that contains this hotfix."
Anyway; here is the link to this hotfix :
KB979917 - QFE for Sharepoint issues - Perf Counter fix & User Impersonation
FIX: A hotfix that provides a method to support the token authentication without transport security or
message encryption in WCF is available for the .NET Framework 3.5 SP1
(http://go.microsoft.com/fwlink/?LinkID=166231).
By the way, it seems you do not need to install it manually since it should be done by the SharePoint
2010 prerequisites software installation.
9 Microsoft SharePoint Server 2010 Installation
9.1 Installing the SharePoint Prerequisites
Double click the installation package to launch the installation of Microsoft SharePoint Server 2010
The SharePoint 2010 installation Wizard is opening
Click the "Install Software Prerequisites" in order to update, complete and check the previous preparation
described in the previous sections of this post. The Microsoft SharePoint Product and technologies 2010
Preparation Tool is opening
You should obtain this screen if you followed the operations previously described in this post.
When the installation of the SharePoint files is finished you are asked to continue with the SharePoint
Products Configuration Wizard.
Do not continue with the Wizard but cancel it otherwise you will have an issue due to the current
installation described in this post.
In the SharePoint 2010 version, you are not allowed as before to mount a Farm installation on a single
machine using local accounts.
If you had continued with the wizard you would have been stopped in the configuration by the following
issue:
the specified user Administrator is a local account. Local accounts should only be used in stand alone
mode.
Fortunately there is a workaround to succeed in obtaining a Farm environment using local accounts as we
used to have in the previous version that I have found in this post:
Single Server Complete Install of SharePoint 2010 using local accounts
I will show it bellow, but first of all, let us create the sevice accounts we need for this.
9.3 Creating several service accounts - about least priviliege administration policy
In the post concerning the Installation of the SharePoint 2010 Beta version, I used a single local account
that was local administrator of the machine, but for this installation, I have chosen to use 3 local accounts
in order to be compliant with the least priviliege administration policy.
This policy requires service accounts not to be administrator of any server of a farm, and that each
service or process runs using a distinct account.
I advice to do it not only for the QA or production environement but also for development environment,
and this for two reasons:
1. First, doing this will help you to debug because the traces of errors in the SharePoint log or in the
event wiever sometimes report the name of the involved account and it will be easier to debug an
issue if you have a precise information and not always a reference to the unique "Administrator"
local account.
2. Second, using the same system of accounts within the development machines and the QA and
production ones can help you to prevent some bugs. Some bugs are due to the fact that the
security used for service accounts are different on the development environment and the QA and
production ones. So it is better if a bug linked to this security configuration occurs in your
development machines than in the QA or worse in the production environement.
For these two reasons, thus, I personally think it is a good practice to have the same service accounts
configuration in all your environments even on the development ones.
Regarding the least priviliege administration policy, The minimal SharePoint installation requires us to
create 2 local accounts :
1. One is for the process of the IIS Application Pool of the central administration. Assume we call it
SPS_Farm
2. The second will be used for the process of the IIS Application Pool of the first Web Application if it
is isolated in its own Application Pool. Assume we call the first Web Application WebApp-80
because it will use the 80 port, let us call this account SPS_WebApp-80.
So let us create these two accounts and configuring them in order password never expires.
New-SPConfigurationDatabase
You will be then prompt for the system account credential. It is now the time to pass the credential of the
SPS_FARM service account. Don't forget the machine (domain) name otherwise you will get an exception
of the SharePoint shell.
Then you are asked for a passphrase. You can use P@ssw0rd that matches the security policies
required.
At this step of the installation you can check that two operations has been performed behind the scene.
Two databases has been created in the database server referenced in the shell window. There is at this
point no difference with MOSS 2007 instalation.
3 web services has been created in IIS with 3 distinct application pools for each. That is a new feature of
SharePoint 2010.
Let the option "Do not disconnect from this server farm" checked.
Then you will be prompted to chose the Central Administration Site port number. I personally always use
55555 for the configuration of all my development environments in order to type the same Url on all my
Virtual Machines.
Let the default NTLM value for the "Authentication provider", Kerberos requires network configuration we
cannot perform in the current environment anyway.
The wizard, then, summarize your choices.
When you click "Finish" to close the wizard, the Central Administration Site is opening, and you are
prompted for credentials
Another page let you choose between configuring your farm yourself or by using a wizard.
When this choice is made, you display for the first time the brand new Welcome Page of SharePoint 2010
Central Administration.
As there is sometimes concern with the SharePoint Services installation with Windows 2008 Server R2,
you should check that the services installation has completed successfully.
On SharePoint 2010 Central Administration Home Page under the System Settings section click Manage
services on server.
You should see this screen that confirms that SharePoint Services installation has completed
successfully.
10 Creating your first site in Microsoft SharePoint Server for Internet Sites
Enterprise 2010
10.1 Creating a managed local account for SharePoint 2010
Now we have to perform operations in order the previously created local account SPS_WebApp-80 be
referenced as a managed account by SharePoint 2010.
So reopen the SharePoint 2010 shell windows and type the following:
I have personally chosen to create it on the default IIS web site, and as a personal usage
named it "Web App - 80"
let the Application pool default settings
named the content database "WSS_Content_WebAppp-80"
You notice then that you have the previously service account available as a SharePoint 2010 managed
account to be the account under the which the process of the new Application Pool will run .
You are then prompted the changes are processed
Click "OK" to close the wizard and to be taken back to the Web Application Management Page where you
can see the new SharePoint 2010 Web Application.
Now, if we go to check what have been done behind the scene in ISS we will notice that we can retrieve a
trace for our SharePoint 2010 managed local accounts:
Last, if now you use the SPS_FARM SharePoint 2010 managed local account to sign in to the Central
Administration:
You will notice that you are not connected as SPS_Farm, but as System Account.
This account is a Farm administraor account used ONLY to administrate the Farm using the Central
Administration Web site. As it is not a local administrator of the server it cannot be used to run the
SharePoint 2010 Configurqtion wizard, neither the obsolete stsadm or psconfig tools, nor the SharePoint
2010 management shell. And there are operations that are no more available from the central
administration web site when you are logged in with this account, as "Manage Services on Server".
10.3 Creating your first Site Collection for SharePoint 2010
From the Central Administration Home Page, click on "Create site collections" in order to proceed to the
creation of your first SharePoint 2010 Site Collection.
Then, click the "Create site collections" link under the "Site Collections" section. You are taken to the
"Create Site Collection" page.
I have personally chosen to create a team site called "SharePoint 2010" team site"
When launching the creation, you are prompted the changes are processed
When clicking on this site link, you can display your first SharePoint 2010 site.
Well done !
As it would be interesting to have a way to send and receive e-mails inside our
development environement you can continue by doing this other tutorial:
Installing and configuring SMTP and POP3 e-mail for SharePoint 2010
And if you plan to migrate to a SharePoint 2010 you can take a look at this post:
Customizing and branding the wiki pages for a SharePoint 2010 Team Site
The following is the previous version of this post that was describing the installation process for the
previous Beta version. I let it as an archive :
I have read here and there that SharePoint Services installation does not work for Windows 2008 Server
R2. I encountered this problem once for an installation but it actually does work.
I have updated this post with a screen shot that shows what you have to see in order to check that all
services are actually properly installed.
see :
8.4 Running the SharePoint Products Configuration Wizard
see :
7.6 hotfix for the token authentication in WCF
1 - Introduction
For those who have the chance to be allowed to download the SharePoint 2010 Beta because they
benefit of an MSDN subscription or because they are employed by a company that is a Microsoft partner,
here is a way to install the Beta version of SharePoint 2010 in order to test it.
As usual I will do my best to supply a step by step tutorial as detailed as possible which demonstrates
how to install 2010 SharePoint Bêta on Windows server 2008 R2.
The environment I propose to mount in this tutorial is a development environment that uses a SharePoint
2010 Beta Farm installation on a single computer using an unique local administrator account.
The SharePoint 2010 content databases will run on a SQLServer 2008 Standard Edition Database
Engine.
I personally have not a MSDN subscription to date (but maybe have it soon) but my company is a
Microsoft partner, so I had the chance to have the Beta version of SharePoint but for the OS, I chose to
take advantage of testing the new version of SharePoint by testing in the same time the Windows 2008
Server R2 OS because Microsoft provides presently an 180 days evaluation version of it.
As you certainly know, SharePoint 2010 requires a 64 bits OS to run.
Therefore, I have chosen to create the Virtual Machine with VMware Workstation 6.5.3 because it is to
date the only way of making run an 64 bit OS guest on a 32 bits OS host.
I will check if it is possible to mount an image with the free VMware Player product in order this tutorial do
not require any purchase for a developer that has the benefits of the SharePoint Beta download. If it is
possible, I will publish about it later.
I have verified that you can actually also create a Virtual Machine running Windows 2008 Server R2
64 bits on a 32 bits host by using the free version of VMware:
...]
Last, if you want to install SharePoint 2010 using Domain Accounts, you can visit the post of Jeremy
Thake, very useful with treeview menu listing all the operations to be performed:
When you click "Finish", the installation begins by loading the files.
Then, you have to choose the version of your Operating System.
Do not choose a Web Server version otherwise you will not be able to add an "Application Server" role to
the server later.
Choose the Full Installation of the Enterprise Version.
The Easy install will install the OS automatically and in my case it did it in approximately 30 minutes!
Then you can access to your new server. You will see the "Initial Configuration tasks".
After you have completed the installation of Windows Server® 2008 R2, and before you deploy the new
server in your enterprise, some configuration is required to identify the computer to other computing
resources on your network, secure the computer, enable administrators to perform tasks on the computer,
and customize the computer by adding server roles and features.
You can complete these tasks by using commands in the Initial Configuration Tasks window, which opens
immediately after the operating system installation is complete.
The Initial Configuration Tasks window opens at each startup, unless the Do not show this window at
logon check box is selected.
If you want to open this windows manually run this command:
C:\Windows\System32\Oobe.exe
3 Configuring the server - Standard Configuration Operations
3.1 Hardware Acceleration
In order to accelerate your Virtual Machine you have to perform the following operations :
Right click your desktop and choose "Screen resolution".
Then, click
Troubleshoot tab
Change Settings button
You will access to the "Display Adapter Troubleshooter" dialog.
Set the cursor to the Full position.
Do not look for any product key, as said before, you do not need any, just click next.
The activation will be done automatically through Internet. You will notice then the activation number and
the number of days remaining on the bottom right corner of the desktop.
3.3 Changing Computer Name
Now, click the "Provide computer name and domain" link,then set your new Virtual machine name.
1. Click Start, point to Administrative Tools, and then click Server Manager.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you
want, and then click Continue.
3. Under Security Summary, click Configure IE ESC.
4. Under Administrators, click On (Recommended) or Off, depending on your desired
configuration.
5. Under Users, click On (Recommended) or Off, depending on your desired configuration.
6. Click OK.
7. Restart Internet Explorer to apply Enhanced Security Configuration.
G
4 Configuring the server - Configuration Operations for SharePoint (MOSS
2007 or SharePoint 2010)
4.1 Adding Server Roles and Roles Services - Application Server - Web Server
On the Initial configuration task windows, click "Add Roles"
The "Add Roles" Wizard is opening.
Check the check box for Application Server.
The wizard opens a modal dialog for the Required Features
Click "Next"
The Select Role Services for Web Server (IIS) Role is displaying, but just let the default options.
The next section will detail the required things to do in order to be compliant with these requirements. As
we install SharePoint on Windows 2008 Server R2 and because we have run the latest updates, most of
the required add in will be useless.
7 Configuring the server - Configuration Operations for SharePoint 2010
Beta 1
7.1 Downloading and installing SQL Server 2008 SP1
First, we have to update the previously installed SQL Server with the SP1 downlodable at :
SQL Server 2008 Service Pack 1
Do not forget to choose the x64 package
7.3 Downloading and installing SQL Server 2008 Analysis Services ADODM.NET
For ending with the products related to SQLServer 2008 download and install the SQL Server 2008
Analysis Services ADODM.NET. Here is the direct link to the download:
ADOMD.NET
Here is the screenshot after the download.
it seems that the link supplied by MSDN and by the page "Determine hardware and software
requirements (SharePoint Server 2010)" are not leading to the correct update for the R2 version of the
OS.
As referenced by Jeremy Thake in his post, I think the good update is to find at:
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=23806
You can find the complete explanation regarding this update on the SharePoint Team Blog:
Installation notice for the SharePoint Server Public Beta on Microsoft Windows Server 2008 R2 and
Microsoft Windows 7
8 Microsoft SharePoint Server for Internet Sites Enterprise 2010 Beta
Installation
8.1 Installing the SharePoint Prerequisites
Double click the installation package to launch the installation of Microsoft SharePoint Server for Internet
Sites Enterprise 2010 Beta
You should obtain this screen if you followed the operations previously described in this post.
8.2 Installing the SharePoint Files
Back to the SharePoint 2010 Installation wizard, click the "Install SharePoint Server" link. The launched
wizard requires the product key.
When the installation of the SharePoint files is finished you are asked to continue with the SharePoint
Products Configuration Wizard.
Do not continue with the Wizard but cancel it otherwise you will have an issue due to the current
installation described in this post.
In the SharePoint 2010 version, you are not allowed as before to mount a Farm installation on a single
machine using local accounts.
If you had continued with the wizard you would have been stopped in the configuration by the following
issue:
the specified user Administrator is a local account. Local accounts should only be used in stand alone
mode.
Fortunately there is a workaround to succeed in obtaining a Farm environment using local accounts as we
used to have in the previous version that I have found in this post:
Single Server Complete Install of SharePoint 2010 using local accounts
New-SPConfigurationDatabase
You will be then prompt for the system account credential. In our case to go fast and not start explaining
the "least privileges administration policy" just type the administrator login and password the which you
are logged with.
Then you are asked for a passphrase. You can use P@ssw0rd that matches the security policies
required.
At this step of the installation you can check that two operations has been performed behind the scene.
Two databases has been created in the database server referenced in the shell window. There is at this
point no difference with MOSS 2007 instalation.
3 web services has been created in IIS with 3 distinct application pools for each. That is a new feature of
SharePoint 2010.
Let the option "Do not disconnect from this server farm" checked.
Then you will be prompted to chose the Central Administration Site port number. I personally always use
55555 for the configuration of all my development environments in order to type the same Url on all my
Virtual Machines.
Let the default NTLM value for the "Authentication provider", Kerberos requires network configuration we
cannot perform in the current environment anyway.
The wizard, then, summarize your choices.
When you click "Finish" to close the wizard, the Central Administration Site is opening, and you are
prompted for credentials
When this choice is made, you display for the first time the brand new Welcome Page of SharePoint 2010
Central Administration.
As there is sometimes concern with the SharePoint Services installation with Windows 2008 Server R2,
you should check that the services installation has completed successfully.
On SharePoint 2010 Central Administration Home Page under the System Settings section click Manage
services on server.
You should see this screen that confirms that SharePoint Services installation has completed
successfully.
9 Creating your first site in Microsoft SharePoint Server for Internet Sites
Enterprise 2010
9.1 Creating your first Web Application for SharePoint 2010
On the default page of the SharePoint 2010 Central Administration, click the "Manage Web Application"
link in the "Application Management" section
On the "Manage Web Application" page click the "New" menu entry then click "New Web Application"
I have personally chosen to create it on the default IIS web site, and as a personal usage
named it "Web App - 80"
let the Application pool default settings
named the content database "WSS_Content_WebAppp-80"
You are then prompted the changes are processed
Click "OK" to close the wizard and to be taken back to the Web Application Management Page where you
can see the new SharePoint 2010 Web Application.
9.2 Creating your first Site Collection for SharePoint 2010
From the Web Application Management Page click the "Application Management" link in the left menu in
order to proceed to the creation of your first SharePoint 2010 Site Collection.
Then, click the "Create site collections" link under the "Site Collections" section. You are taken to the
"Create Site Collection" page.
I have personally chosen to create a team site called "SharePoint 2010" team site"
When launching the creation, you are prompted the changes are processed
then prompted on that the site was created successfully.
When clicking on this site link, you can display your first SharePoint 2010 site.
Well done !
10 Aknowledgments
Thanks to Neil 'The Doc' Hodgkinson for his post solving the local accounts issue. He updated his post
yesterday, and you can find a link to a nice article about the SharePoint 2010 installation.
Thanks to Augusto Simoes for his post that makes me save a lot of time
Good to see others documenting their installs, did you manage to get User
Profiles working with this?
http://www.sharepointdevwiki.com/display/spadmin2010/2009/11/21/How+to
+install+SharePoint+2010+Public+Beta+on+Windows+Server+2008+R2
Regarding the second update (KB971831), it seems that the link supplied by
MSDN and by the page "Determine hardware and software requirements
(SharePoint Server 2010)" are not leading to the correct update for the R2
version of the OS.
As referenced by you in your post, I think the good update is to find at:
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?
DownloadID=23806
Its name: Windows6.1-KB976462-x64
I performed the installation today and it ran perfectly well.
3 - Last, I am very interested in this new concept of Delegate User for the Farm, it
seems to be what we did previously for implementing Least Privileges
Administration Policy.
I wonder if you have to perform this task if you have already done it during the
installation.
cheers.
Marc
Hello Marc,
The update KB976462 it is a fix for WCF match after the update (KB971831).
Very nice site. http://blogs.dotnet-france.com/collaboration
Pleasure.
NOVEMBER 26, 2009 4:49 PM
titab said...
I am not sure this happens in all installations but at least in mine it happened. I
had to manually disable the 32-Bit Applications in all the application pools used
by SP before I could start loading the Central Admin site. So, it's worth checking
that setting before thinking the installation went wrong.
I have tried your How to and I am stuck, I am in the SP Shell trying to make the
Database, and I am getting this error,
New-SPConfigurationDatabase : Exception of type
'Microsoft.SharePoint.SPException' was thrown At Line:1 char:28
+ New-SPConfigurationDatabase <<<<
+CategoryInfo : InvalidData: Microsoft.Share...urationDatabase:
SPCmdletNewSPConfigurationDatabase [New-SPConfigurationDatabase],
SPCmdletException
+FullyQualifiedErrorID:
Microsoft.SharePoint.PowerShell.SPCmdletNewSPConfigyrationDatabase
Hi Rob,
Marc
Sewy said...
databaseServer: server_name\db_name
i.e.: sp1\MOSS_DB
I was getting the same error Rob was, the InvalidData. I realized the account I
was trying to use for the farm credentials did not have permission to my SQL
Server. After giving the account permissions it worked.
Satish said...
HI
i had followed the installation prcedure
i run all the commands after typing username and password it is asking
passpharse ( I gave my system passw0rd At that i am getting this error
hello,
I had some problems installing in the SQL serve 2008
RonaldTeussink said...
hello,
I followed the post and got it all working on a VMWare 7 Workstation (on
Windows 7 x64), the only thing I was unable to do is set the Hardware
acceleration in paragraph 3.1. Directly after installing W2K8 Server R2 and
before the setup of VMWare tools ends you are able to adjust this acceleration,
but after the VM resets and you return to the settings, the button is greyed out (so
you can't adjust the hardware acc. performance anymore). Any ideas if this was
intended in version 7?
Carlos said...
javier said...
I was suffering the Invalid data: exception untill I opened TCP 1433 port on my
SQL Server box.
SharePoint is on a different box.
Also created an SPN for SQL Server since I am usin a domain user account for the
service.
MARCH 15, 2010 12:18 PM
satish said...
HI
Anonymous said...
Hi,
I am new to share point wanted
to install share point server 2010
i have a 32 bit processor and 32 bit operationg system(Xp)
now would like to use vmware to install 64 windows server 2008 and share point
server respectively but when trying to install its is showing a error is there any
way i can solve this problem
Regards,
Micheal
Hi,
I think the problem is that your computer CPU is not a supported 64-bit
processor.
[...
When you power on a virtual machine with a 64-bit guest operating system,
Workstation performs an internal check: if the host CPU is not a supported 64-bit
processor, you cannot power on the virtual machine.
VMware also provides a standalone utility that you can use without Workstation
to perform the same check and determine whether your CPU is supported for
Workstation virtual machines with 64-bit guest operating systems. You can
download the 64-bit processor check utility from the VMware Web download
site.
..]
Marc
Anonymous said...
Anonymous said...
Marc,
I could install windows server 2008 in my system using vmware 7 still have to
install moss 2010 there was some setting in bios vt settings i enabled it and it
worked fine
thanks
Michael,
I should add something in my post regarding hardware requirement for the host
computer and Virtualization Technology enabling in the bios...
happy you could succeed in making all work properly, and you had not to buy a
new computer...
Wishing you plenty of good time with the SharePoint 2010 new platform.
Cheers.
Marc
Salut Marc,
Thank you very much for the excellent guide. One observation I can make is that
VMWare is not the only products that allows to run 64bits VM on 32 bits OS.
Virtualbox also does that and even before VMWare. Virtualbox (free) has
comparable features than VMWare Workstation 7x. Have a look, you'll need
some adjustments to get used to VB GUI and config, this is just a habits change.
When done, you'll be pleased by the level of performance and features. As
shocking as it may seem, VMWare is no longer the king in Desktop Virtualization.
Virtualbox progresses at a stunning pace and is available under several platforms
- and easy to install - including Linux and Mac.
Hi,
thank you for the information. In my mind Virtualbox was equal to Mac, but you
learnt me today this is wrong. And it seems to be Open Source.
I didn't know all that...
Cheers
Marc
Anonymous said...
Hey!
I need help regarding New-SPConfigrationDataBase issue.
when i give information without administration permissions management shell, i
got error that Requested register access is not allowed.
when i open managemnt shell as a administrator permission then i got nothing
error but my domain name and user name with line 1 and char 28 ...etc....
how can i solve this issue...'
I followed this link to install sharepoit 2010
http://mosshowto.blogspot.com/2009/11/installing-sharepoint-2010-windows-
2008.html
Results were good till 8.3, but at 8.3 i stuck...
so can you pls help to figure out my probelm...
Best Regards
Kazmi
Hi,
Can you send me the screen shot of the powershell prompt ? (marccharmois at
hotmail dot com)
And we also have to check Event Viewer and SharePoint logs and if the databases
was created within SQL Server Database Engine...
good courage...
Marc
Sper said...
Do I need to give the 2 created account permission to acces the sql database? If
so, how do I do this? I haven't got a clue of SQL.
Hi Sper,
2 - Does the account you use to launch the SharePoint shell have sysadmin
privileges for SQL? Normally you should have an account that is local
administrator of the machine and you should have used this account, both to
install SQL Server, and to install SharePoint binaries and launch the SharePoint
Shell.
Marc
Sper said...
Sharepoint is installed using the same user account which is the local
administrator.
Hi Sper,
can you check the SQL version and service pack version?
Are you sure that you did not create a named instance when you installed SQL
Server?
Can you check that Named Pipes are activated both in the server features and in
SQL?
If you try to perform the SharePoint configuration several times you have to
check if databases have been created and delete them before each new trial.
You can also check Event Viewer and especially SharePoint logs to find more
information about this issue.
Good luck!
Marc
Sper said...
Hi Sper,
happy to help, I did the same few years ago and I spoiled hours to understand
what was going wrong so I did not forget ;-)
I am sure there is a syntax to call the named instance when the SharePoint Shell
ask for the Database, otherwise you could not use named instances with
Sharepoint 2010, so you have to search for this in MS documentation or perform
tests.
Try to pass as parameter the named instance, or severName/NamedInstance or
anything else that make sense...
Maybe if you display the Shell help on the command, it is explained. Maybe there
is a parameter for this...
Perform tests and don't forget to delete created databases between tests, but I
don't think there will be databases created before anyway because it fails before
creation.
And most of all, when you find the syntax, let us know it within a comment on
this blog or a link to a post on your blog...
Cheers!
Marc
Sper said...
Grtz,
Sper said...
Grtz,
Hope someone will find this usefull.
Cheers,
Marc
POST A COMMENT
CREATE A LINK
<< Home
ABOUT ME
MARC CHARMOIS
ARCHIVES