Thursday 3 March 2011

Retrieve MySite data for updated user profile (login name - AD) in AD

Hello there, it’s been very long that we have updated the blog. I’m sure all the geeks know about SharePoint 2010 by now and few start posting things to the community.

Recently I had a query from an organization about My Site profile as explained below;
Scenario
The domain user profile updated with “Display Name”, “Login Name” in active directory for existing domain user. The user already have MySite/Personal site created in SharePoint 2010 platform with my contents such as document libraries and list so on.

I had “SPTEST1” user login name in AD and created SharePoint 2010 personal site as “http://intranet:81/personal/sptest1” and later updated the user to “JHON MATT” in active directory. When the updated (user login name “Domain\jmatt”) access the mysite/personal site at SharePoint 2010, the “Display Name” remains the same.

After changing the properties in domain, the user “Display Name” still remains same as previous.
I need my user’s “Display Name” and “Url” to be changed to “Jhon Matt” and “http://intranet:81/personal/jmatt

Resolution

1. Soon after the profile update in AD, please do “Incremental Profile Synchronization”

2. Change the personal site url in Central Administration site – Application Management – (UserProfileServiceApplication) – Manage User Profiles under People

3. Find the user by entering the user’s name
4. Highlight and click the down arrow – click “Edit My Profile”

5. Change the personal site url from “/personal/sptest1 - to - /personal/jmatt”

6. Let, Jhon Matt login to domain with updated user name (login name) and create new mysite/personal site at SharePoint 2010 My Site Host

7. Go to Central Administration web site – Backup and Restore – Export site or list – Select an “OLD” personal site created for “SPTEST1” as shown below. You even can select granular level lick document library (In this scenario I have selected personal document library which has got sample text file)


8. Once successful, you will have 2 files created in above mentioned backup location as “sham.cmp and sham.cmp.export”



9. Open SharePoint PowerShell from start and type “Import-SPWeb
Identity: http://intranet:81/personal/jmatt
Path: \\INTRANET\backup\SharePoint\sham.cmp and ENTER
as shown below screenshot

10. Additional file will be created in backup location folder


11. You can review the log files for any errors and launch the user’s personal site as http://intranet:81:/personal/jmatt , you will get the contents from OLD site in updated user’s
personal


12. At your My Site web application you will have 2 personal sites for this user. Once you have successfully backup and restored the contents to the updated profile personal site for the user, you may delete the OLD site.


That’s it.
I hope this would help for guys out there ……..

Cheers !!!!




Thursday 15 July 2010

This Site and This List Scopes Not Working in MOSS 2007

Hi Guys,
Long time didn't post useful stuff in our site. I had to work on many projects and documentations, so that didn't have a chance to get hold with sharepointlk blog. Sorry for that..

Recently I'm assigned to a project for Intranet on SharePoint 2007. I managed to deploy all the components of MOSS 2007 on Windows Server 2008 using SharePoint 2007 SP2 setup.

While working on the site and adding web parts, I discovered that I couldn't do search within the site or list in particular sub site or the list.

Was struggling and going through various blogs and resolved the issue, so I thought of share the workaround with you guys...

My environment;
• Windows Server 2008 32 bit
• MOSS 2007 with SP2
• Installed Arabic language Pack (MOSS 2007 & WSS 3.0)
• Arabic Language Pack SP (MOSS 2007 & WSS 3.0)
• Latest Cumulative update for MOSS 2007 & WSS 3.0
(June Cumulative Update (CU)
Released June 29, 2010
This update provides hotfixes for Windows SharePoint Services 3.0 (KB 983311) and Office SharePoint Server 2007 (KB 983310))


After having installed above mentioned software and hotfixes, I have created the collaboration website and few sub sites with in the same web application

Configured alternative access mapping for my sever name and was able to access successfully. When access the SharePoint web site being in the windows sever 2008, it is keeping prompting me for user name and password and finally its gives me blank white page but I can access the website using the local machine name and it succeeded without any errors. I could access the web site from client machines using AAM name and was successful.

So I ignored accessing the web site from windows sever 2008.

Configured the search and started the crawl, I got access denied error for the web site I created in SharePoint even though the default content access account has full rights to the web site, the error is;

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (The item was deleted because it was either not found or the crawler was denied access to it.)




Then I change the content source from AAM name to local machine name, crawl was success and I could do the search using central search site but I couldn’t do the search using “This Site & This List”.



Was going through some blogs and MS articles, found below workaround to solve the issue for above mentioned “Access Denied” error and search no result when you search using “This Site & This List

To resolve the issues, you need to disable the loop back check in the registry mentioned in below article
http://support.microsoft.com/kb/896861

That fixed the issue I had and I was able to crawl the website using AAM and could search “This Site & This List” Search

Hope above information is useful

Cheers !!!

Tuesday 6 April 2010

2010 First 5 key Improvements….............................

1. No timeouts - So yes, in the previous 2007 in place upgrade, there would be failures based on timeouts related to things like large lists.

2. Continue on failure – Think of it as on error resume next. In the previous if you ran into something missing or something unexpected upgrade would fail.


3. Resume – After a failure you will now be able to resume where you left off.

4. Error Logging – So the error logging is much better. It’s in it’s own file so that definitely makes it much easier to troubleshoot and identify issues.

5. Better status output – new stsadm command localupgradestatus which allows you to see the progress of the upgrade after the configuration wizard has been run. In fact the new UI in Central Admin, Upgrade Status page in 2010 will also allow you to see the database upgrade status.

Sunday 4 April 2010

FQDN and SharePoint 2007 Server Name

Dear Guys,

Recently I was working on a project where it involves 17 SharePoint 2007 Server Farm. As I did the architecture of the solution, my client wants to keep their entire internet facing Web Front End SharePoint Servers on DMZ. We managed to install the WFEs on DMZ with additional domain controller on DMZ which has one way trust for internal network DC. Microsoft NLB had configured for these SharePoint Web Front End Servers in DMZ.

Everything was working smoothly until I configure the Search Service for the farm.

Scenario is;

Web Front Ends (DMZ Zone)
Index Server (Intranet Zone)
Central Admin Server (Intranet Zone)
Database Server - Cluster (Intranet Zone)

When I access the website search, it was giving me the following error;

Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.

I have checked the services for search and was running and search service was started as well. I recreated the search and did the full crawl again but no luck. Even I recreated the SharedService associated with it and still no luck.

I just the browsed the web site using machine name which has the web application hosted from a client which is residing intranet network and search was working perfectly. when I browse the website using named configured in NLB, search is not working and giving the same error message as Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.


I logged into one of the web front end servers and tried the search, still it is giving me the same error message in search result page.

Went through "Event Viewer" and discovered some warning messages saying that the Web Front End Server (in DMZ) could not contact the INDEX server located in intranet network. In my firewall, I have opened all the ports from WFEs to SharePoint Server Farm Servers.

When did the PING command from WFEs server to INDEX Server located in intranet network by MACHINE NAME (Example IndexServer), I got request time out as reply.

BUT

When I did the PING command from WFEs Server to INDEX Server located in intranet network by FQDN NAME (Example IndexServer.domain.com), I got reply successfully.

DISCOVERED

I added the INDEX Server name in all the WFEs' host file as NetBIOS name for its IP Address HURRAY !!!!! Search was working smoothly as expected.

CONCLUSION

SharePoint 2007 Technologies Servers does not identify machine with FQDN names and it only recognize with NetBIOS name of Farm servers.

Hope above information would help you guys when you all into DMZ related deployment for SharePoint 2007 Farm.

Cheers !!!!

Thursday 10 September 2009

Restore MOSS 2007 and Project Server 2007 Issue "Page Cannot Be Displayed"

Hi Guys

Long time we didn’t update our blog with latest activities. That’s due to my other colleague relocated and I was busy with customers’ task and projects. Hope you guys are fine with your tasks.

Lately I was working on backup & restore for MOSS 2007 and Project Server 2007 at customer site as disaster recovery for these two web applications which used heavily on their internal collaborations and project managements.

Was struggling to get these two web applications to get up and running their staging environment for disaster recovery purpose. Let me share with you the activities I have performed at site to make MOSS 2007 & Project Server 2007 restore on staging environment. These steps will not have detailed step by step, it will let you have the idea of high level steps.

Scenario

MOSS 2007

•Single server (Stand alone installation)

•SP 1 (12.0.0.6129)

•SQL 2005 Express edition (MOSS 2007 Internal Database Version 9.00.4035.00)

Project Server 2007

•MOSS 2007 stand alone installation with SP1 (12.0.0.6219)

•Project Server 2007 Stand alone installation

•SQL 2005 Express

•Upgraded to SQL 2005 Enterprise Edition with SP1 (SQL Server 2005 Enterprise edition with SP1 version 9.00.2047.00)


For MOSS 2007 backup & restore, I didn’t have any problems since it was .mdf & .ldf DB attached from SQL Server Management Studio, still I will share what I did.

Production Server

1.Stop windows SharePoint Timer Services

2.Stop World Wide Web Services

3.Make copy of Content DB (.mdf & .ldf) or else you still make .bak file using SQL Server 2005 Management Studio


Staging Server

1.Install and configure the SharePoint Server stand alone deployment. When you install basic installation, it will create web application and site collection for you. Everything will be configured automatically

2.From the central admin site, remove the content DB attached to you web application

3.Attach the copied .mdf & .ldf from SQL Express Management Studio

4.From central admin site, in Content DB link, attach the new created content DB in SQL Management Studio

5.Note:- If unable to attach from GUI, please follow the below STSADM command line to attach the content DB for web application

STSADM –o addcontentdb –url –databasename -databasename

6.You can restore from .bak file as well if you have taken SQL Server back up from production server

7.Once everything is completed, you can browse the site and you will see exact look & feel as you production (note:- if you custom solutions deployed, you should deploy all the custom applications before you browse the site after restore)


That was smooth backup and restore for the MOSS 2007 stand alone farm installation


Project Server 2007 backup & restore

Production Server

1.As I mentioned in above steps for backing up MOSS 2007, followed the same steps for backing up Project Server 2007 as well. Only different is you have additional 4 databases for Project Server 2007, such Published, Archived, Draft and Reporting

2.Backup content DB and Project Server 2007 databases as mentioned above

3.You can take .mdf & .ldf file for above databases or you may create SQL Server backup (.bak) for all the databases by using management studio


Staging Server

1.Install MOSS 2007 (Stand alone installation. Recommended to follow the version of the MOSS 2007)
2.Run the SharePoint Server Technologies Wizard

3.Upgrade SQL 2005 Express Edition by using UPGRADESKU = 1 key along with the setup. Start -> Run -> Brows the setup.exe from SQL 2005 enterprise edition CD -> type SKUUPGRADE = 1 -> enter

4.Please make sure to select the instance for OFFICESSEREVERS for MOSS 2007 installation

5.After the completion of UPGRADE, run SharePoint Server Technologies Wizard again

6.Patch the SQL Server 2005 with SP1

7.Run SharePoint Server Technologies Wizard again

8.Install Project Server 2007

9.Run the SharePoint Server Technologies Wizard again

10.Remove the content DB from web application

11.In SQL Management Studio, overwrite the existing content DB with backup made from production (Stop WWW and SharePoint Timer Services if necessary)

12.If it’s more than 5 GB of content DB, from GUI you may not be able to add the content DB to web application. If so please add using STSADM Command as follows;

STSADM –o addcontentdb –url –databasename -databasename

13.You may receive error in command line saying upgrade completed with errors please refer the log file located in 12 hive.

14.Using SQL Management Studio, attach copied .mdf & .ldf files for the Project Server 2007 web application

15.Delete the /pwa provisioned site using GUI (Central Admin) or STSADM (If created, default installation will create it automatically or sometimes it may failed)

16.Recreate the /pwa site on default web application.

17.Once recreated successfully, edit newly provisioned /pwa site link using SharedServices Provider for assigning attached Project databases.

Note:- if you have modified your production /pwa site by adding links, web parts and addition documents on main site, make sure to take production /pwa backup using STSADM.

Once you have provisioned new /pwa site on staging, you can overwrite the newly provisioned /pwa site using STSADM restore overwrite option. So you will have all your production documents, links and web parts on restored /pwa site.


18.Start the services if you have stopped and try access the default site you overwrite with the backup

-------------------- IF YOU STILL UNBALE TO BROWS THE SITE---------------------------

If you get “Page cannot be displayed” when your browsing, please follow the steps that worked for me in live environment;


1.Detach the content DB and attach again

2.Change the site collection administrator to current domain admin or the service account you gave while installing the MOSS 2007

------------------------------IF ITS STILL NOT WORKING----------------------------------------

If you still receive the “Page cannot be display” when you brows the site, follow the below steps;

1.Delete the web site in IIS using central admin “Delete Web Application” link.
Make sure to delete the web site from the IIS, not the content database for the web application

2.Create new web application using existing content DB


3.Now you should be able to access the site without problem


Hope these tips are useful when troubleshooting the restore process. If you have clarification, just mail us using this web site.

Cheers !!!!

Sunday 23 August 2009

SharePoint Services 3.0 Event ID 3670

I was suffering of event id 3670 & failure Audit id 18456 since last 2 days and wanted to get away from it. I was searching all the forums and blogs regarding that and couldn't find a resolution for the error. All the blogs and forums are mentioning to reinstall and attach the content DB.


My Scenario is,

Installed Windows SharePoint Services 3.0 with SP2
Installed SQL Management Studio for DB administration
Windows 2003 Standard R2 with SP 2
.Net Framework 3.5


I have installed the above mentioned applications and service packs for document archival in WSS 3.0. The default installation path for the WSS 3.0 DBs are in your windows folder location where C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data

So I wanted to change the DB location and I used SQL management studio to change it. I have copied all the DBs from C:\ drive to my F:\ drive where it has more space to accommodate the DB growth. After copying the DBs, by opening the SQL management studio, I have attached all the DBs (Please stop the Windows SharePoint Timer Services from Services before copying or attaching the DBs) except SharePoint_AdminContent_XXXXXXXX.

Once the attachment of DBs (without SharePoint_AdminContent_XXXXXXXX), I started the Windows SharePoint Timer Services and start working on my WSS 3.0 sites and uploading documents.

Later some days, I just want to do some admin task in Central Administration Web Site and I couldn’t access the site at all. Then I went through the Event viewer and found out following Errors loaded in my Event Viewer;

SQL Database 'SharePoint_Config_af70289d-9151-473c-b0df-8fe74e809ac0' on SQL Server instance 'SERVER\Microsoft##SSEE' not found. Additional error information from SQL Server is included below.
Cannot open database "SharePoint_Config_af70289d-9151-473c-b0df-8fe74e809ac0" requested by the login. The login failed.


With Failure Event as following

Event Type: Failure Audit
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (4)
Event ID: 18456
Date: 4/21/2009
Time: 2:37:36 PM
User: PBTF\apbyrum
Computer: THOTH
Description:
The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: PBTF\APByrum, [CLIENT: ].

My Event viewer was full with above errors and wanted a resolution badly.

Solution

• Detach the 'SharePoint_Config_af70289d-9151-473c-b0df-8fe74e809ac0 DB from copied location (from F:\ Drive location). While detaching the DB, please select “Drop Connections” and click OK


• Attach the 'SharePoint_Config_af70289d-9151-473c-b0df-8fe74e809ac0 DB from original location (from C:\Window location)

• Attach the SharePoint_AdminContent_97c95945-3cec-49c7-8eb9-25bb2a6f5b98

After doing above tasks and I could be able to access the Central Administration site and there were no errors in my event id.

Hope the above information will be useful for guys who need some tips to troubleshoot. This above resolution works for my scenario without a doubt.

Cheers !!!

Thursday 20 August 2009

How to connect SQL Embedded Edition using SQL Management Studio

If you have installed WSS 3.0 with Embedded SQL edition and you wanted to get connected to the instances with MS SQL Managemen Studio for manageing the DB, Please follow the below steps to reach there.

Here is how we connect to the Embedded SQL instance:

We can create a Server Alias for the "MICROSOFT##SSEE" named instance.

1. Run "cliconfg" on the box from the command line or from Start --> Run

2. In the "SQL Server Client Network Utility" console, click the Alias tab.

3. Create a new Server alias.

4. Server alias: \
MICROSOFT##SSEE

5. Replace with the exact server.
Network libraries: Named Pipes
Server name: .\MICROSOFT##SSEE
Pipe name: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query


6. Then open SQL 2005 management studio, input \MICROSOFT##SSEE as Server Name.

Now you can use SQL 2005 management studio to connect to the SQL data for SharePoint site successfully.

Hope above information is helpful

Cheers !!

Friday 31 July 2009

Top SharePoint Internet Facing Website In Real-world

Top Website SharePoint For Internet Sites In Real-world

Hi,

Some SharePoint Internet facing sites.

very very interesting............

http://www.wssdemo.com/Pages/topwebsites.aspx

SharePoint Server 2010 Preliminary System Requirements

SharePoint Server 2010 Preliminary System Requirements, announced by sharepoint team.

(Artical on SharePoint Team Blog)


SharePoint Server 2010 will be 64-bit only.
SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
In addition to the requirements listed above we also wanted to share with you some preliminary detail about SharePoint Server 2010 browser compatibility.

To ensure the best possible experience across multiple browsers we’re focusing our SharePoint 2010 engineering efforts on targeting standards based browsers (XHTML 1.0 compliant) including Internet Explorer 7, Internet Explorer 8 and Firefox 3.x. running on Windows Operating Systems. In addition we’re planning on an increased level of compatibility with Firefox 3.x and Safari 3.x on non-Windows Operating Systems. Due to this focus Internet Explorer 6 will not be a supported browser for SharePoint Server 2010.

So, what can you do today to get into the best shape for SharePoint Server 2010?

Start by ensuring new hardware is 64-bit. Deploying 64-bit is our current best practice recommendation for SharePoint 2007.
Deploy Service Pack 2 and take a good look at the SharePoint 2010 Upgrade Checker that’s shipped as part of the update. The Upgrade Checker will scan your SharePoint Server 2007 deployment for many issues that could affect a future upgrade to SharePoint 2010.
Get to know Windows Server 2008 with SharePoint 2007, this post is a great starting point.
Consider your desktop browser strategy if you have large population of Internet Explorer 6 users.
Continue to follow the Best Practices guidance for SharePoint Server 2007.
Keep an eye on this blog for updates and more details in the coming months.
Below are a few common Q&A’s (which we’ll add to as required)



Q: What about Internet Explorer 6 and SharePoint 2010 publishing sites?
A: The Web Content Management features built into SharePoint 2010 will provide a deep level of control over the markup and styling of the reader experience. These features will enable customers to design pages that are compatible with additional browsers for viewing content, including Internet Explorer 6. A standards based browser such as Internet Explorer 7, Internet Explorer 8 or Firefox 3.x will be required to author content.

Q: Is Internet Explorer 6 officially supported by Microsoft?
A: Official Microsoft Product Support for Internet Explorer 6 follows the lifecycle of the Operating System with which it was shipped. In order for customers to receive product support through the Mainstream Support and Extended Support phases, they need to have installed a supported Service Pack. For example, customers who are using Windows XP must transition to Service Pack 3 by July, 2010 and are eligible to receive support for Internet Explorer 6 until April, 2014.

You can find additional information on Microsoft’s Support Lifecycle Policy including specific dates, product information and support offerings here: http://support.microsoft.com/gp/lifepolicy.

Q: Why are you only supporting the 64-bit versions of SQL Server 2005 or 2008 for SharePoint Server 2010?
A: This decision was based on our current test data for SharePoint Server 2010 and real world experience from customers running SharePoint Server 2007 with 32-bit SQL Server. SharePoint performance and scalability can benefit significantly from 64-bit SQL Server and the throughput increases are significant enough for us to make the difficult decision to only support SharePoint Server 2010 on 64-bit SQL Server 2005 or 2008. It has been our strong recommendation for some time that SharePoint Server 2007 customers take advantage of 64-bit SQL Server due to the inherent performance and scale benefits it can provide.

for more.......


http://blogs.msdn.com/sharepoint/archive/2009/05/07/announcing-sharepoint-server-2010-preliminary-system-requirements.aspx

Wednesday 29 July 2009

SharePoint White Papers

Hi,


It's important the we all should follow some guide in terms of deployment scenarios while binging i found some interesting papers where you will find interesting.

SharePoint White Papers click here

Advantages of 64-bit hardware and software (Office SharePoint Server 2007) TechNet Article

Updated: 2009-04-02

It is often more comfortable to continue to use something that is familiar and that we know works. The widespread adoption of the 64-bit environment for use with Microsoft Office SharePoint Server 2007 has been slow to happen, probably because of the investment in time, money, and effort that went into installing and configuring 32-bit hardware and software. The main concerns appear to be that migration to 64-bit will be expensive, difficult, time-consuming, and incompatible with existing software. This article is intended to show that these concerns are exaggerated and far outweighed by the potential benefits.

Understanding the 64-bit environment

The 64-bit environment consists of both hardware and software components. Although the conversion to 64-bit hardware alone may improve performance somewhat, optimum benefit is derived only when 64-bit hardware and software are working together.

64-bit hardware

Although 64-bit processing capability has been used in specialized applications for decades, only in the last several years has it been widely available for Intel-based computers. The majority of new servers that are being sold now are 64-bit servers; however, most of the computers that are currently used as Windows-based servers still use a 32-bit architecture. The prevalence of 32-bit servers puts some limitations on the speed, reliability, and scalability of applications that require a lot of resources, such as Office SharePoint Server 2007.

In computer architecture, the term 64-bit most frequently refers to the design of the central processing unit (CPU), but can also relate to the size of the external data bus of the computer. Among other benefits, a 64-bit CPU can calculate individual tasks two times as fast as a 32-bit model and can address significantly more random access memory (RAM) than the 4-gigabyte (GB) limit imposed by 32-bit processors. A server that has both a 64-bit CPU and a 64-bit data bus is better able to process and manage the large database files associated with Office SharePoint Server 2007.

Not all 64-bit computers are the same. Intel's Itanium series of 64-bit processors uses a proprietary design that is not compatible with Microsoft SharePoint Products and Technologies. Be sure to check the processor type when you acquire hardware for use in a Office SharePoint Server 2007 farm.

64-bit software

The benefits of 64-bit hardware can only be fully obtained if the software that you install is designed to use all the features of the hardware. Software intended for 32-bit computers, although compatible, will generate few, if any, of the desired benefits when it is installed on a 64-bit computer. Office SharePoint Server 2007 and all its prerequisite operating system and database software have installation options for 64-bit computers.

Windows Server 2003 and Windows Server 2008 offer 64-bit versions of the Standard and Enterprise editions. If you are a volume-licensing customer who wants to upgrade to 64-bit, the switch from 32-bit to 64-bit or Itanium editions is free. The Standard edition supports up to 32 GB of RAM on 1-way to 4-way servers. The Enterprise edition offers better support for large databases and up to 2 terabytes of RAM on 1-way to 8-way servers. For more information about Windows Server in a 64-bit environment, see Benefits of Microsoft Windows x64 Editions (http://go.microsoft.com/fwlink/?LinkId=147235).

The 32-bit and 64-bit versions of SQL Server are based on a common architecture. The 64-bit versions of SQL Server are optimized to run on servers that use AMD Opteron, AMD Athlon 64, Intel Xeon with support for Intel Extended Memory 64 Technology (EM64T), or Intel Pentium IV with support for EM64T. For more information about SQL Server in a 64-bit environment, see Advantages of a 64-bit Environment (http://go.microsoft.com/fwlink/?LinkId=147234).

There are no differences in the feature set or the installation process between the 32-bit edition and 64-bit edition of Office SharePoint Server 2007.

Advantages of 64-bit hardware and software

Memory addressability

  • Physical memory

    A 32-bit system architecture can directly address only a 4-GB address space. A 64-bit system architecture that is running a 64-bit edition of Windows Server can support up to 1,024 GB of both physical and addressable memory.

  • Virtual memory

    The 64-bit editions of Windows Server can address 16 terabytes of virtual memory by using a flat addressing model. Virtual memory is divided equally between virtual address space for applications and the operating system. Even 32-bit applications can benefit from increased virtual memory address space when they are running in a 64-bit environment. For example, although a 32-bit application is still restricted to 4 GB of virtual memory, it no longer has to share that memory space with the operating system. As a result, it receives an effective increase in available virtual memory.

  • Continuous memory

    Poor performance in 32-bit systems is often not the result of a lack of available memory, but the unavailability of large enough blocks of continuous memory. In a typical Office SharePoint Server 2007 deployment, Windows, Internet Information Services (IIS), common language runtime (CLR), ASP.NET, SharePoint Products and Technologies, SSPs, and MDACs can all claim a portion of a server's available virtual memory and can leave a 32-bit address space quite fragmented. When the CLR or SharePoint services request new memory blocks, it can be difficult to find a 64-MB segment in the crowded 32-bit address space. A 64-bit system offers practically unlimited address space for user mode processes.

Better parallel processing

A server that is using 32-bit architecture is limited to 32 CPUs. Improvements in parallel processing and bus architectures enable 64-bit environments to support as many as 64 processors and provide almost linear scalability with each additional processor.

Faster bus architecture

A 64-bit architecture provides more and wider general-purpose registers, which contribute to greater overall application speed. When there are more registers, there is less need to write persistent data to memory and then have to read it back just a few instructions later. Function calls are also faster in a 64-bit environment because as many as four arguments at a time can be passed in registers to a function.

More secure

The 64-bit editions of Windows Server offer the following enhanced security features:

  • Buffer overflow protection

    A buffer overflow occurs when a data buffer is congested with more data than it is designed to handle. In 64-bit editions of Windows Server, the first parameters of a procedure call are passed in registers. As a result, it is less likely that the buffer will overflow, because the correct values have to be set up in registers and the variables and addresses have to be aligned on the stack.

  • Data execution protection

    The 64-bit processors made by AMD and Intel include hardware support for data execution prevention (DEP). Windows Server uses DEP to prevent malicious code from being able to execute, even when a buffer overrun occurs. Even without a processor that supports DEP, Windows Server can detect code that is running in memory locations where it should not be.

  • Patch Guard

    Microsoft Patch Guard technology prevents non-Microsoft programs from patching the Windows kernel. This technology prevents kernel mode drivers from extending or replacing kernel services, including system service dispatch tables, the interrupt descriptor table (IDT), and the global descriptor table (GDT). Third-party software is also prevented from allocating kernel stacks or patching any part of the kernel.

Better scalability

In a 64-bit environment, not only can database servers gain nearly unlimited virtual memory address space, but they also gain support for more physical memory. It is possible for a 64-bit server that is running 64-bit editions of Windows Server and SQL Server to get very large working data sets entirely into RAM, thereby improving performance and scalability. In addition, the number of application servers that are required to support a given user base can be substantially reduced because a 64-bit environment does not require worker processes to cycle as often. This reduced cycling results in fewer lost connections, improved I/O handling, and a better user experience.

Lower total cost of ownership

All the benefits of 64-bit operation that are listed in the previous sections enable you to do more with less. A 64-bit environment allows you to manage more data, serve more users, and run more applications while using less hardware. By reducing hardware, you are also able to reduce license, operations, and infrastructure costs. It takes up less floor space in your data center and costs less to maintain. Finally, because a Office SharePoint Server 2007 farm that uses 64-bit hardware and software provides more room for growth, you can spend less over time on equipment because the life cycle of your equipment is likely to be longer.

A 64-bit environment might not be ideal for every situation

Disadvantages of a 64-bit environment

Typically, 64-bit servers require more virtual memory than 32-bit servers. The 64-bit framework reserves memory in segments that are based on the number of processors. As a general rule, a 4-processor server should have a minimum of 5 GB of virtual memory and an 8-processor server should have a minimum of 6 GB.

The ability of 64-bit applications to access a larger physical and virtual memory space means that address tables are larger and can result in a larger data-transaction overhead. As a result, small or repetitive tasks may run marginally slower than in a 32-bit environment.

It is a common practice to repurpose idle server equipment. Therefore, if your organization has a lot of 32-bit servers available, it may be difficult to justify purchasing new 64-bit hardware on which to run Office SharePoint Server 2007. When you have to choose between purchasing new 64-bit equipment and repurposing old 32-bit servers, consider the potential for operational savings over time by using 64-bit servers and software.

Some third-party software or Office SharePoint Server 2007 features will not work in 64-bit mode. However, future versions of SharePoint Products and Technologies will be optimized for 64-bit operation and will not support 32-bit environments at all.

Deploying a 64-bit system

New deployment

Deployment of Office SharePoint Server 2007 in a new 64-bit farm differs very little from a 32-bit deployment. The planning documentation available for new deployments includes information on configuring your farm to make optimum use of the increased capabilities of 64-bit hardware and software. For more information about planning and deploying Office SharePoint Server 2007 in a 64-bit environment, see Before You Begin with SharePoint Server 2007 (http://go.microsoft.com/fwlink/?LinkID=98564).

Conversion of an existing deployment

It is not necessary to switch your whole Office SharePoint Server 2007 deployment to 64-bit servers all at once. In most cases, 32-bit and 64-bit servers can operate comfortably within the same farm, and performing the conversion incrementally can spread the cost out over time and help maintain continuity of service throughout the transition.

To find a detailed procedure for migrating Office SharePoint Server 2007 to a 64-bit environment, see Migrate an existing server farm to a 64-bit environment (Office SharePoint Server 2007).

Incremental migration to 64-bit servers

If you choose to migrate your servers to 64-bit servers one at a time, it is good to know which servers will benefit most from the switch. By migrating the servers in a certain order, you can optimize the transition and take advantage of the performance improvements immediately. The following servers are listed in the order of those that benefit most from conversion to 64-bit:

  1. Database servers

    SQL Server is very processor and memory intensive. Migrating to a 64-bit server can result in immediate benefits by allowing the database server to support more databases while handling more connections and more transactions.

  2. Front-end Web servers and application servers

    Worker processes can always benefit from additional memory. The more services and applications that you run on your server, the more they will all benefit from the improved memory management and higher memory limits a 64-bit environment offers. When you convert front-end Web servers to 64-bit, be sure to migrate all of them at the same time.

    We recommend that you do not mix 32-bit and 64-bit front-end Web servers for long-term deployment. Server loads can become unbalanced if one or more servers are performing better than the rest.

  3. Application servers running Excel Calculation Services

    Excel calculation services are mostly a burden to the CPU. The faster architecture of the 64-bit processor and external data bus will yield a significant performance improvement.

  4. Index servers

    Index servers require a fast processor and rapid disk I/O. They also have to maintain a large number of connections simultaneously. A 64-bit architecture offers the improved memory management and large data bus that can help reduce crawl times.

  5. Query servers

    Query servers tend to be the quietest servers in the farm and may benefit the least from conversion to 64-bit hardware. However, in cases where the query server is processing a large number of search requests at a time, the increase in performance will be noticeable.

32-bit software on 64-bit hardware

It is possible to run 32-bit software on 64-bit hardware. The 64-bit editions of Windows Server include the Windows on Windows 64-bit (WOW64) translation layer, which can emulate a 32-bit operating system. In many cases, WOW64 enables 32-bit software and 64-bit software to run simultaneously on the same computer. However, only 64-bit versions of SharePoint Products and Technologies can be run on 64-bit editions of Windows Server.

Mixing 32-bit and 64-bit servers

Some important considerations when you are running a mixed 32-bit and 64-bit farm are as follows:

  • Do not use the /3GB switch in Windows Server 2003

    On a 32-bit server with a total of 4 GB of virtual address space, the /3GB switch can optimize performance by transferring 1 GB of virtual address space from the kernel to the user mode processes. This is not recommended on 64-bit hardware because it leaves only 1 GB available to the kernel. The large address tables that are used by 64-bit hardware can cause that address space to be depleted. As a result, the computer may become destabilized. For more information, see the Knowledge Base article The Windows Server 2003 /3GB switch is not supported in Windows SharePoint Services 2.0 or in later versions or in SharePoint Portal Server 2003 SP2 or in later versions (http://go.microsoft.com/fwlink/?LinkId=105919).

  • Maintain 32-bit or 64-bit homogeneity at each topology layer

    You can deploy an Office SharePoint Server 2007 farm on a mix of 32-bit and 64-bit servers provided that you maintain architecture homogeneity at each topology layer. For example, you can use 64-bit database servers with 32-bit front-end Web servers, or 64-bit application servers with 32-bit servers that are running Excel Services. However, we do not recommend combining 32-bit and 64-bit front-end Web servers within the same farm.

  • Mixing 32-bit and 64-bit servers can increase the maintenance overhead for the farm

    In mixed 32-bit and 64-bit scenarios, it is necessary to manage things such as third-party applications, custom solutions, software patches, and updates independently for each platform.

Summary

If the 32-bit servers in a deployment are performing adequately and the users are satisfied with the operation of their sites, applications, and search requests, there may be no urgency to convert the Office SharePoint Server 2007 deployment to 64-bit. However, if performance of the server farm is not meeting your expectations or customers' expectations, if the user base is growing rapidly, if the application pools are recycling more and more often, or if a scheduled equipment upgrade is approaching, it may be time to advance to a new and growing standard and migrate the equipment and software to 64-bit.

Tuesday 21 July 2009

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6


This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.

http://support.microsoft.com/kb/896861

Workaround

Method 1: Specify host names
loadTOCNode(2, 'workaround');

Note We recommend that you use this method.To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:


Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
Right-click MSV1_0, point to New, and then click Multi-String Value.

Type BackConnectionHostNames, and then press ENTER.

Right-click BackConnectionHostNames, and then click Modify.

In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.

Quit Registry Editor, and then restart the IISAdmin service.

Back to the top
Method 2: Disable the loopback check
loadTOCNode(2, 'workaround');

Follow these steps:



Click Start, click Run, type regedit, and then click OK.

In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.

Type DisableLoopbackCheck, and then press ENTER.

Right-click DisableLoopbackCheck, and then click Modify.

In the Value data box, type 1, and then click OK.

Quit Registry Editor, and then restart your computer.

MOSS Search Appliance

Microsoft in the UK have broken new ground, partnering with SCAN technolgies to develop a Search Appliance based on MOSS. The appliance will be offered across the MOSS SKU range and hardware specification can be tailored to meet customer requirements.







If you are interested in this then please email Mike using mikepal'AT'microsoft.com or call Pete at SCAN on +44 7976 312 862

Thursday 16 July 2009

Change the default 10 MB limit for saving a site as template

Today i was trying to save a site template with a capacity os 78 MB didnt work till i change the limitation of the default size.

This is ware STSADM comes in....

stsadm -o setproperty -pn max-template-document-size -pv 524288000

This will set a 500 MB limit instead, which is apparently the maximum value you can specify.

found this after binging all over...........

Stsadm Technical Reference for Windows SharePoint Services 3.0

STSADM is a great tool for SharePoint administrator, we may be asking why we need a command line tool ? answer is we do all our day to day administrations using UI, when you do configurations over UI there are configuration errors mistakes occurs very often, when you get familiar with STSADM command line tool the chances of configuration errors are I would say 90 % less than using UI, and its meant for administration purpose.

here we go with some Index of STSADM

Technet Link
http://technet.microsoft.com/en-us/library/cc288413.aspx

SharePoint STSADM Technical Refarance Chart
http://technet.microsoft.com/en-us/windowsserver/sharepoint/dd418924.aspx


NameDescriptionMore information

Activatefeature

Activates a feature in the feature collection.

Activatefeature: Stsadm operation (Windows SharePoint Services)

Addalternatedomain

Adds an internal URL and maps it to one of the five URL zones of a Web application or external resource.

Addalternatedomain: Stsadm operations (Windows SharePoint Services)

Addcontentdb

Creates a new content database or adds a database that needs to be upgraded when the urldatabasename and parameters are specified.

Addcontentdb: Stsadm operation (Windows SharePoint Services)

Addpath

Adds a managed path inclusion to a Web application.

Addpath: Stsadm operation (Windows SharePoint Services)

Addpermissionpolicy

Adds a user to a policy role for the Web application based on the specified permission level name and corresponding zone.

Addpermissionpolicy: Stsadm operation (Windows SharePoint Services)

Addsolution

Adds a solution file to the solution store.

Addsolution: Stsadm operation (Windows SharePoint Services)

Addtemplate

Adds a site template to the template gallery.

Addtemplate: Stsadm operation (Windows SharePoint Services)

Adduser

Adds a user account to the specified site collection and assigns it to the specified site group.

Adduser: Stsadm operation (Windows SharePoint Services)

Addwppack

Adds a Web Part package to the server Web Part gallery.

Addwppack: Stsadm operation (Windows SharePoint Services)

Addzoneurl

Configures the public URL and maps it to one of the five URL zones of a Web application or external resource.

Addzoneurl: Stsadm operation (Windows SharePoint Services)

Authentication

Authentication provides the user identity input to the authorization process which determines what actions the current user is allowed to perform on a given object.

Authentication: Stsadm operation (Windows SharePoint Services)

Backup

Describes how to back up a site collection, an individual database, a Web application, or an entire farm.

Backup: Stsadm operation (Windows SharePoint Services)

Backuphistory

Displays a history of backup and restore operations that have been run.

Backuphistory: Stsadm operation (Windows SharePoint Services)

Binddrservice

Registers a data retrieval service adapter.

Binddrservice: Stsadm operation (Windows SharePoint Services)

Blockedfilelist

Enables an administrator to add or delete a file type to the blocked file types list for a Web application.

Blockedfilelist: Stsadm operation (Windows SharePoint Services)

Changepermissionpolicy

Updates the Web application policy level for a user to enable a change to specific permission levels the user is assigned.

Changepermissionpolicy: Stsadm operation (Windows SharePoint Services)

Copyappbincontent

Copies Web application–specific files, such as page resource (*.resx) files from their respective locations in the 12\CONFIG folder to the correct location in each Web application on the computer.

Copyappbincontent: Stsadm operation (Windows SharePoint Services)

Createadminvs

Displays the port number to the SharePoint Central Administration Web site.

Createadminvs: Stsadm operation (Windows SharePoint Services)

Creategroup

Lets site collection administrators create new groups from any site collection.

Creategroup: Stsadm operation (Windows SharePoint Services)

Createsite

Creates a site collection at the specified Uniform Resource Locator (URL) with the specified user as site collection owner and site collection administrator.

Createsite: Stsadm operation (Windows SharePoint Services)

Createsiteinnewdb

Creates a site at the specified Uniform Resource Locator (URL) and creates a new content database using the user name and password you specify.

Createsiteinnewdb: Stsadm operation (Windows SharePoint Services)

Createweb

Creates a subsite at the specified Uniform Resource Locator (URL).

Createweb: Stsadm operation (Windows SharePoint Services)

Databaserepair

Detects and removes orphaned items from content databases in Windows SharePoint Services.

Databaserepair: Stsadm operation (Windows SharePoint Services)

Deactivatefeature

Deactivates a feature in the feature collection.

Deactivatefeature: Stsadm operation (Windows SharePoint Services)

Deleteadminvs

Unprovisions the SharePoint Central Administration Web site from the local machine.

Deleteadminvs: Stsadm operation (Windows SharePoint Services)

Deletealternatedomain

Deletes an internal URL from a URL zone.

Deletealternatedomain: Stsadm operation (Windows SharePoint Services)

Deleteconfigdb

Unprovisions the local machine from the farm and deletes the configuration database (but does not drop the configuration database).

Deleteconfigdb: Stsadm operation (Windows SharePoint Services)

Deletecontentdb

Detaches a content database when the Web application, database name, and database server are specified.

Deletecontentdb: Stsadm operation (Windows SharePoint Services)

Deletegroup

Deletes a group created in Windows SharePoint Services 3.0.

Deletegroup: Stsadm operation (Windows SharePoint Services)

Deletepath

Removes an included path from the list of paths managed by Windows SharePoint Services.

Deletepath: Stsadm operation (Windows SharePoint Services)

Deletepermissionpolicy

Deletes a permission policy for a user from the site collection by specifiying the URL name and user login.

Deletepermissionpolicy: Stsadm operation (Windows SharePoint Services)

Deletesite

Deletes the site collection with the specified URL from the Web application.

Deletesite: Stsadm operation (Windows SharePoint Services)

Deletesolution

Removes a Windows SharePoint Services Solution Package (*.wsp) from the solution store.

Deletesolution: Stsadm operation (Windows SharePoint Services)

Deletetemplate

Deletes a specified site template from the site template gallery.

Deletetemplate: Stsadm operation (Windows SharePoint Services)

Deleteuser

Deletes a user account from the specified site collection and specified site.

Deleteuser: Stsadm operation (Windows SharePoint Services)

Deleteweb

Deletes a subsite using the specified Uniform Resource Locator (URL).

Deleteweb: Stsadm operation (Windows SharePoint Services)

Deletewppack

Removes the Web Parts in a Web Part package from a virtual server.

Deletewppack: Stsadm operation (Windows SharePoint Services)

Deletezoneurl

Deletes a public URL and the zone to which it is mapped.

Deletezoneurl: Stsadm operation (Windows SharePoint Services)

Deploysolution

Deploys files related to a solution from the configuration database to individual front-end Web servers in the farm.

Deploysolution: Stsadm operation (Windows SharePoint Services)

Deploywppack

Deploys a Web Part package.

Deploywppack: Stsadm operation (Windows SharePoint Services)

Disablessc

Disables Self-Service Site Creation for the specified Web application.

Disablessc: Stsadm operation (Windows SharePoint Services)

Displaysolution

Displays specific solution or Web Part information in a solution store.

Displaysolution: Stsadm operation (Windows SharePoint Services)

Enablessc

Enables Self-Service Site Creation for the specified Web application.

Enablessc: Stsadm operation (Windows SharePoint Services)

Enumallwebs

Displays the IDs and site map status for all site collections and subsites in the content database.

Enumallwebs: Stsadm operation (Windows SharePoint Services)

Enumalternatedomains

Lists the internal URLs and specifies the URL zones and public URLs to which they are mapped.

Enumalternatedomains: Stsadm operation (Windows SharePoint Services)

Enumcontentdbs

Enumerates all content databases in the Web application.

Enumcontentdbs: Stsadm operation (Windows SharePoint Services)

Enumgroups

Lists all the groups in Windows SharePoint Services 3.0.

Enumgroups: Stsadm operation (Windows SharePoint Services)

Enumroles

Lists the site groups that are available for use in a particular site or subsite.

Enumroles: Stsadm operation (Windows SharePoint Services)

Enumservices

Lists all the services in the Web application within a farm.

Enumservices: Stsadm operation (Windows SharePoint Services)

Enumsites

Displays a list of sites that are hosted in a Web application. To find the sites that need to be upgraded, use the redirectedsites parameter.

Enumsites: Stsadm operation (Windows SharePoint Services)

Enumsolutions

Enumerates the list of Windows SharePoint Services Solution Package (*.wsp) and Web Part packages located in the solution store of the farm.

Enumsolutions: Stsadm operation (Windows SharePoint Services)

Enumsubwebs

Lists the subsites that have been created immediately below a particular site.

Enumsubwebs: Stsadm operation (Windows SharePoint Services)

Enumtemplates

Lists the site templates that have been submitted to the global site template catalog.

Enumtemplates: Stsadm operation (Windows SharePoint Services)

Enumusers

Lists the users of a particular site collection or subsite.

Enumusers: Stsadm operation (Windows SharePoint Services)

Enumwppacks

Lists the Web Part packages currently in the server Web Part gallery.

Enumwppacks: Stsadm operation (Windows SharePoint Services)

Enumzoneurls

Lists all of the public URL and the zones to which they are mapped.

Enumzoneurls: Stsadm operation (Windows SharePoint Services)

Email

Sets the e-mail configuration settings for your server.

Email: Stsadm operation (Windows SharePoint Services)

Execadmsvcjobs

Permits a user to run any administrative service job in which the Windows SharePoint Services Administration (SPAdmin) service has been disabled.

Execadmsvcjobs: Stsadm operation (Windows SharePoint Services)

Export

Exports site and subsite data from your Windows SharePoint Services 3.0 installation.

Export: Stsadm operation (Windows SharePoint Services)

Extendvs

Extends a Windows SharePoint Services 3.0 Web application and creates a new content database.

Extendvs: Stsadm operation (Windows SharePoint Services)

Extendvsinwebfarm

Extends a Windows SharePoint Services 3.0 Web application for use in a server farm.

Extendvsinwebfarm: Stsadm operation (Windows SharePoint Services)

Forcedeletelist

Allows a user to delete a list that might appear to be in a corrupted state.

Forcedeletelist: Stsadm operation (Windows SharePoint Services)

Getadminport

Returns the administration port for Windows SharePoint Services.

Getadminport: Stsadm operation (Windows SharePoint Services)

Getsitelock

Retrieves the lock status of a site.

Getsitelock: Stsadm operation (Windows SharePoint Services)

Import

Imports site and subsite data from your Windows SharePoint Services 3.0 installation.

Import: Stsadm operation (Windows SharePoint Services)

Installfeature

Installs a feature.

Installfeature: Stsadm operation (Windows SharePoint Services)

Listlogginglevels

Lists the current event log and trace log logging levels for each diagnostic logging category that is registered in a farm.

Listlogginglevels: Stsadm operation (Windows SharePoint Services)

Localupgradestatus

Displays the farm and local server components that need to be upgraded.

Localupgradestatus: Stsadm operation (Windows SharePoint Services)

Managepermissionpolicylevel

Enables an administrator to manage the policy levels for a Web application.

Managepermissionpolicylevel: Stsadm operation (Windows SharePoint Services)

Mergecontentdbs

Permits a site collection to be moved from one content database to another when the souredatabasename and destinationdatabasename parameters are specified.

Mergecontentdbs: Stsadm operation (Windows SharePoint Services)

Migrateuser

Migrates a user account in Windows SharePoint Services 3.0 to a new user name and binary ID.

Migrateuser: Stsadm operation (Windows SharePoint Services)

Preupgradecheck

Runs rules that are intended to assist administrators in preparing for upgrade from Windows SharePoint Services 3.0 and related products to future version of SharePoint and Technology products.

Preupgradecheck: Stsadm operation (Windows SharePoint Services)

Provisionservice

Prepares sites and content databases before moving to a new Web application by setting up the profile and membership synchronization service.

Provisionservice: Stsadm operation (Windows SharePoint Services)

Refreshdms

Refreshes the Directory Management Service if a database is restored or moved to a location where the incoming e-mail settings are not correct.

Refreshdms: Stsadm operation (Windows SharePoint Services)

Refreshsitedms

Performs the same function as the Refreshdms operation but on a site collection level.

Refreshsitedms: Stsadm operation (Windows SharePoint Services)

Registerwsswriter

Enables the Windows SharePoint Services VSS Writer service (known as WSS Writer service) on any front-end Web server.

Registerwsswriter: Stsadm operation (Windows SharePoint Services)

Removedrservice

Removes a data retrieval service from the list of data retrieval services.

Removedrservice: Stsadm operation (Windows SharePoint Services)

Removesolutiondeploymentlock

Removes the solution deployment lock for the specified server or all servers from the back-end database.

Removesolutiondeploymentlock: Stsadm operation (Windows SharePoint Services)

Renameserver

Changes the name of the specified server in the configuration database.

Renameserver: Stsadm operation (Windows SharePoint Services)

Renamesite

Changes a URL of a host-named site collection to a new URL.

Renamesite: Stsadm operation (Windows SharePoint Services)

Renameweb

Changes the URL of a subsite.

Renameweb: Stsadm operation (Windows SharePoint Services)

Restore

Explains how a restoration of a site collection, an individual database, a Web application, or an entire farm is performed.

Restore: Stsadm operation (Windows SharePoint Services)

Retractsolution

Retracts the specified solution’s deployment, and removes files from the front-end Web server.

Retractsolution: Stsadm operation (Windows SharePoint Services)

Retractwppack

Retracts the deployment of a specified Web Part package.

Retractwppack: Stsadm operation (Windows SharePoint Services)

Scanforfeatures

Scans for new features in the file system, and if new features are present, installs them.

Scanforfeatures: Stsadm operation (Windows SharePoint Services)

Setadminport

Changes the default zone Uniform Resource Locator (URL) and/or application pool located on the SharePoint Central Administration Web site.

Setadminport: Stsadm operation (Windows SharePoint Services)

Setconfigdb

Creates a new configuration database in a farm or joins the local computer to an existing farm's configuration database.

Setconfigdb: Stsadm operation (Windows SharePoint Services)

Setlogginglevel

Sets the Windows event log and trace log logging level for one or more diagnostic logging categories registered in the farm.

Setlogginglevel: Stsadm operation (Windows SharePoint Services)

Setsitelock

Sets a value that specifies whether the site collection is locked and unavailable for read or write access.

Setsitelock: Stsadm operation (Windows SharePoint Services)

Setworkflowconfig

Enables or disables the workflow settings.

Setworkflowconfig: Stsadm operation (Windows SharePoint Services)

Siteowner

Sets the primary or secondary administrator of a site collection.

Siteowner: Stsadm operation (Windows SharePoint Services)

Spsearch

Manages the Windows SharePoint Services Search service.

Spsearch: Stsadm operation (Windows SharePoint Services)

Spsearchdiacriticsensitive

Enables or disables the diacritic sensitivity setting.

Spsearchdiacriticsensitive: Stsadm operation (Windows SharePoint Services)

Syncsolution

Performs a synchronization of the Windows SharePoint Services Solution Package (WSP) solutions stored in the configuration database with the files stored on disk.

Syncsolution: Stsadm operation (Windows SharePoint Services)

Trimauditlog

Lets an administrator delete audit entries older than a certain date, as specified using the enddate parameter.

Trimauditlog: Stsadm operation (Windows SharePoint Services)

Tzmove

Allows an administrator to update data that is affected by a change in the start and/or end of Daylight Saving time (DST).

Tzmove: Stsadm operation (Windows SharePoint Services)

Unextendvs

Removes Windows SharePoint Services 3.0 from a particular Web application.

Unextendvs: Stsadm operation (Windows SharePoint Services)

Uninstallfeature

Removes the specified feature definition from the collection of feature definitions in the farm.

Uninstallfeature: Stsadm operation (Windows SharePoint Services)

Unregisterwsswriter

Disables the Windows SharePoint Services VSS Writer service (known as WSS Writer service) on any front-end Web server.

Unregisterwsswriter: Stsadm operation (Windows SharePoint Services)

Updateaccountpassword

Updates the Web application pool passwords.

Updateaccountpassword: Stsadm operation (Windows SharePoint Services)

Updatealerttemplates

Lets an administrator update custom changes to the Alerttemplates.xml file.

Updatealerttemplates: Stsadm operation (Windows SharePoint Services)

Updatefarmcredentials

Updates the Web application pool for the SharePoint Central Administration Web site and the Windows SharePoint Services Timer service (SPTimer).

Updatefarmcredentials: Stsadm operation (Windows SharePoint Services)

Upgrade

Upgrades the specified site collection during a gradual upgrade.

Upgrade: Stsadm operation (Windows SharePoint Services)

Upgradesolution

Upgrades an existing solution. The solution to be upgraded could be either deployed or not deployed; however, the immediate or time parameters apply only if the solution has been deployed.

Upgradesolution: Stsadm operation (Windows SharePoint Services)

Upgradetargetwebapplication

Prepares the environment for the gradual upgrade of a specific version 2.0 Web application by moving the existing version 2.0 Web application to a new URL and making a new version 3.0 Web application that is based on the existing version 2.0 Web application and associated settings.

Upgradetargetwebapplication: Stsadm operation (Windows SharePoint Services)

Userrole

Adds or deletes permission levels to site groups.

Userrole: Stsadm operation (Windows SharePoint Services)

Properties

Property nameDescriptionMore information

Alerts-enabled

Turns alerts on or off.

Alerts-enabled: Stsadm property (Windows SharePoint Services)

Alerts-limited

Specifies the number of alerts to which a user can create.

Alerts-limited: Stsadm property (Windows SharePoint Services)

Alerts-maximum

Specifies the maximum number of alerts a user can create.

Alerts-maximum: Stsadm property (Windows SharePoint Services)

Avallowdownload

Specifies whether users can download infected documents to their local computers.

Avallowdownload: Stsadm property (Windows SharePoint Services)

Avcleaningenabled

Specifies whether antivirus cleaning is enabled or disabled.

Avcleaningenabled: Stsadm property (Windows SharePoint Services)

Avdownloadscanenabled

Specifies whether documents are scanned when they are downloaded.

Avdownloadscanenabled: Stsadm property (Windows SharePoint Services)

Avnumberofthreads

Specifies the number of threads to use for antivirus processes.

Avnumberofthreads: Stsadm property (Windows SharePoint Services)

Avtimeout

Specifies how long to wait before an antivirus process times out.

Avtimeout: Stsadm property (Windows SharePoint Services)

Avuploadscanenabled

Specifies whether documents are scanned when they are uploaded.

Avuploadscanenabled: Stsadm property (Windows SharePoint Services)

Change-log-expiration-enabled

Specifies whether change logs are deleted after the time span defined in the Change-log-retention-period: Stsadm property (Windows SharePoint Services) property.

Change-log-expiration-enabled: Stsadm property (Windows SharePoint Services)

Change-log-retention-period

Specifies the amount of time to preserve change logs

Change-log-retention-period: Stsadm property (Windows SharePoint Services)

Command-line-upgrade-running

Specifies whether the upgrade process has already been started.

Command-line-upgrade-running: Stsadm property (Windows SharePoint Services)

Data-retrieval-services-enabled

Turns data retrieval services on or off.

Data-retrieval-services-enabled: Stsadm property (Windows SharePoint Services)

Data-retrieval-services-inherit

Specifies whether the Web application inherits data retrieval service settings that are located on the SharePoint Central Administration Web site.

Data-retrieval-services-inherit: Stsadm property (Windows SharePoint Services)

Data-retrieval-services-oledb-providers

Obsolete.

Not applicable

Data-retrieval-services-response-size

Specifies the response size of the data source that is returned to the data retrieval service.

Data-retrieval-services-response-size: Stsadm property (Windows SharePoint Services)

Data-retrieval-services-timeout

Specifies the request time out setting.

Data-retrieval-services-timeout: Stsadm property (Windows SharePoint Services)

Data-retrieval-services-update

Turns the support for update queries on or off.

Data-retrieval-services-update: Stsadm property (Windows SharePoint Services)

Data-source-controls-enabled

Turns the data source controls on the server on or off.

Data-source-controls-enabled: Stsadm property (Windows SharePoint Services)

Database-command-timeout

Retrieves or sets the wait time before terminating the attempt to execute a command and generating an error.

Database-command-timeout: Stsadm property (Windows SharePoint Services)

Database-connection-timeout

Retrieves an open connection or sets a connection to a Microsoft SQL Server database.

Database-connection-timeout: Stsadm property (Windows SharePoint Services)

Days-to-show-new-icon

Specifies the number of days to display the "New" icon for items added to a Web site.

Days-to-show-new-icon: Stsadm property (Windows SharePoint Services)

Dead-site-auto-delete

Turns on or off the setting to delete the site collection

Dead-site-auto-delete: Stsadm property (Windows SharePoint Services)

Dead-site-notify-after

Specifies the number of days to wait before sending notifications

Dead-site-notify-after: Stsadm property (Windows SharePoint Services)

Dead-site-num-notifications

Specifies the number of notifications to send

Dead-site-num-notifications: Stsadm property (Windows SharePoint Services)

Defaultquotatemplate

Specifies the default quota template to be used when creating new site collection on a specified Web application.

Defaultquotatemplate: Stsadm property (Windows SharePoint Services)

Defaulttimezone

Specifies the time zone for sites that are created in a Web application.

Defaulttimezone: Stsadm property (Windows SharePoint Services)

Delete-web-send-email

Deletes the site collection if use is not confirmed

Delete-web-send-email: Stsadm property (Windows SharePoint Services)

Irmaddinsenabled

Specifies a rights management platform other than Windows Rights Management Server.

Irmaddinsenabled: Stsadm property (Windows SharePoint Services)

Irmrmscertserver

Specifies the location of the Windows Rights Management Services server.

Irmrmscertserver: Stsadm property (Windows SharePoint Services)

Irmrmsenabled

Controls whether the server should use the Windows RMS infrastructure instead of another rights management platform.

Irmrmsenabled: Stsadm property (Windows SharePoint Services)

Irmrmsusead

Specifies that Windows SharePoint Services 3.0 should use the location of the RMS server that is stored in Active Directory, rather than an administrator manually specifying the location of the Windows RMS.

Irmrmsusead: Stsadm property (Windows SharePoint Services)

Job-ceip-datacollection

Specifies the time schedule for when Customer Experience Improvement Program (CEIP) data is collected.

Job-ceip-datacollection: Stsadm property (Windows SharePoint Services)

Job-change-log-expiration

Specifies the time schedule when the change log timer job occurs.

Job-change-log-expiration: Stsadm property (Windows SharePoint Services)

Job-config-refresh

Specifies the schedule for the configuration refresh job.

Job-config-refresh: Stsadm property (Windows SharePoint Services)

Job-database-statistics

Specifies the time schedule when database statistics are collected.

Job-database-statistics: Stsadm property (Windows SharePoint Services)

Job-dead-site-delete

Specifies the frequency interval and time range to delete unused Web sites automatically, for example, "Weekly at Sat 0:00:00".

Job-dead-site-delete: Stsadm property (Windows SharePoint Services)

Job-gradual-site-deletion

Added in the April Cumulative Update to perform gradual deletion of site collections. Lets a site collection to be marked as deleted, which immediately prevents any further access to its content.

Job-gradual-site-deletion: Stsadm property (Windows SharePoint Services)

Job-immediate-alerts

Specifies the frequency to check for alerts that are to be sent immediately.

Job-immediate-alerts: Stsadm property (Windows SharePoint Services)

Job-recycle-bin-cleanup

Specifies the time schedule for a cleanup of the Recycle Bin to occur.

Job-recycle-bin-cleanup: Stsadm property (Windows SharePoint Services)

Job-usage-analysis

Lets an administrator set the time interval for usage processing.

Job-usage-analysis: Stsadm property (Windows SharePoint Services)

Job-watson-trigger

Displays the time schedule of the Windows SharePoint Services Watson Upload job.

Job-watson-trigger: Stsadm property (Windows SharePoint Services)

Job-workflow

Sends the workflow events that have been queued and delivers them to workflows.

Job-workflow: Stsadm property (Windows SharePoint Services)

Job-workflow-autoclean

Specifies the time schedule for when a scan occurs to delete workflow instance data.

Job-workflow-autoclean: Stsadm property (Windows SharePoint Services)

Job-workflow-failover

Specifies a schedule for restarting workflow operations that fail because of external reasons.

Job-workflow-failover: Stsadm property (Windows SharePoint Services)

Large-file-chunk-size

Specifies the amount of data that can be read from the server running Microsoft SQL Server at one time.

Large-file-chunk-size: Stsadm property (Windows SharePoint Services)

Max-file-post-size

Specifies the maximum allowable size for a single upload of content to any site.

Max-file-post-size: Stsadm property (Windows SharePoint Services)

Presenceenabled

Allows users of a SharePoint site to see if other users are online and send instant messages to them.

Presenceenabled: Stsadm property (Windows SharePoint Services)

Recycle-bin-cleanup-enabled

Specifies whether a cleanup to the recycle bin occurs.

Recycle-bin-cleanup-enabled: Stsadm property (Windows SharePoint Services)

Recycle-bin-enabled

Turns the Recycle Bin on or off.

Recycle-bin-enabled: Stsadm property (Windows SharePoint Services)

Recycle-bin-retention-period

Specifies the retention period, in days, of deleted items in the Recycle Bin.

Recycle-bin-retention-period: Stsadm property (Windows SharePoint Services)

Second-stage-recycle-bin-quota

Specifies how much hard disk space is available to a second stage Recycle Bin as a percentage of the quota allotted to the Web application.

Second-stage-recycle-bin-quota: Stsadm property (Windows SharePoint Services)

Presenceenabled

Allows users of a SharePoint site to see if other users are online and send instant messages to them.

Presenceenabled: Stsadm property (Windows SharePoint Services)

Token-timeout

Specifies the amount of time before a user token times out.

Token-timeout: Stsadm property (Windows SharePoint Services)

Usageprocessingenabled

Configures whether the usage analysis process is turned on or off.

Usageprocessingenabled: Stsadm property (Windows SharePoint Services)

Workflow-cpu-throttle

Obsolete.

Not applicable

Workflow-eventdelivery-batchsize

Specifies the paging size for events delivered to a single workflow instance.

Workflow-eventdelivery-batchsize: Stsadm property (Windows SharePoint Services)

Workflow-eventdelivery-throttle

Specifies the number of workflows that can be processed (that is, using the processor, not idle) at the same time across all front-end Web servers.

Workflow-eventdelivery-throttle: Stsadm property (Windows SharePoint Services)

Workflow-eventdelivery-timeout

Specifies the time in which a workflow job must run without the job timing out. If the workflow job does time out, it gets put back in the queue to be run again.

Workflow-eventdelivery-timeout: Stsadm property (Windows SharePoint Services)

Workflow-timerjob-cpu-throttle

Obsolete.

Not applicable

Workitem-eventdelivery-batchsize

Specifies the maximum number of work items that will be paged in to a processing timer job.

Workitem-eventdelivery-batchsize: Stsadm property (Windows SharePoint Services)

Workitem-eventdelivery-throttle

Specifies the maximum number of work items that can be obtained on a given query for work items that are scheduled to run.

Workitem-eventdelivery-throttle: Stsadm property (Windows SharePoint Services)