We are pleased to present below all posts tagged with 'MOSS 2007'. If you still can't find what you are looking for, try using the search box.
During a recent migration, we ran into an issue when attempting to migrate users from one domain to another using stsadm migrateuser. Hopefully this will help any others that are getting this strange error. Our environment was a small MOSS 2007 64-bit farm installed with slipstreamed SP2, with the February 2010 cumulative update applied.
We were moving from an on-premise to Hosted solution, so this required a new domain and user accounts. Since the new domain wouldn’t know anything about the old domain’s user accounts, we added the –ignoresidhistory switch. We ran the following command:
During a recent information architecture project for a client who was migrating data from a single site collection to thirteen site collections, I realized that I would need to delete one of the subsites contained within the original site collection. It would have been nice and simple if I just needed to delete the site collection, but unfortunately this was not the case. The problem was the overwhelming number of sites that needed to be deleted. We all love using the stsadm command line tool, but one shortfall is that you cannot delete a site that contains a subsite. In the past I have bit the bullet and deleted sites, one at at time, using the stsadm –o deleteweb command, but I did not have the time or patience for that in this situation.
After doing some online research I found the answer I was looking for; there “IS” a better way to delete sites in SharePoint
Our team recently finished a significant enterprise MOSS farm migration from a single-server installation to a multi-server farm topology. Once the new farm was architected and constructed, the migration went as smoothly as it could have, with no major obstacles. However, as a day or two passed, a few of the end users began to notice a strange occurrence.
This particular client is a heavy user of the My Sites and My Links functionality. During the migration, we used the User Profile Replication Engine, which is just one component of the SharePoint Administration Toolkit. This allowed us to migrate user profiles, and more importantly, specific user profile properties. The primary reason for this was to avoid an SSP migration, which is where the actual “My Links” are stored.
Recently, we deployed a large project for a multinational corporation and an interesting situation arose during the process. The SharePoint portal for this particular client was accessible externally (outside of their corporate network). This allowed users to access the sites worldwide without having to use a VPN to connect to the corporate network. This is not uncommon in the SharePoint world, and we have implemented and configured a fair number of Extranet portals over the years.
This particular project was very document-centric (as are many in SharePoint), with multiple workflows for approval, updating, publishing, etc. Because of this, the Microsoft Word client was heavily used in the application, and seamless client integration was a critical important requirement.
During beta testing, we discovered two strange occurrences:
1) Emails generated by the automated task creation (for document approval) had a mixture of URLs with http and https.
2) When opening a document for editing/approval, the user sometimes received an error that he/she could not approve or edit the task associated with the document.
Have you ever spent hours tweaking your site footer in the SharePoint master page so that it stays at the bottom of your site, only to find out that when you view it in another browser or screen resolution it jumps back up the page? That’s frustrating to say the least!
In order to fulfill a client requirement on their SharePoint site, I needed to figure out how to accomplish this on a tight deadline. I found a site that provided the perfect solution to my issue. Ryan Fait shows how simple it is to make a “sticky footer”. It works with just a few simple CSS classes and simple HTML markup.
The solution has been tested in IE 5 and up, Firefox, Safari and Opera. It basically counts a negative value from the bottom of your page and sets the footer on top of it. The solution was easy to implement, worked perfectly, and satisfied the client! Thanks Ryan Fait!
The October Cumulative Update (CU) for WSS 3.0 and MOSS 2007 was released on October 27th.
Every two months, Microsoft tries to release updates to the Office product line, including WSS and MOSS. The latest release addresses various issues across the board. Microsoft and the SharePoint product team does a good job with communicating the changes, so I have included the links to “what has been fixed” as well as a post by Joerg Sinemus detailing the installation procedure for the October CU.
I was recently tasked with quickly customizing a SharePoint site to fit the needs of a client. In other words, making a SharePoint site not look like SharePoint. Where do you start? It did not sound like an easy task, but rather a matter that would require a lot of research, trial and error. I was ecstatic to stumble upon a fantastic piece of work from Heather Solomon, a web designer specializing in SharePoint branding, layout and usability. Heather’s Base Master Page Templates strip down master pages for your use with SharePoint 2007 sites, so you don’t have to dig through tedious lines of code and formatting; Heather has done this for you!
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.