To hide fields in the edit and newform pages for a list add the following Javascript to the top on the

default list pages using SPD 

 <script language="javascript" type="text/javascript">

_spBodyOnLoadFunctionNames.push("hideFields");

function findacontrol(FieldName) {

   var arr = document.getElementsByTagName("!");
   // get all comments
   for (var i=0;i < arr.length; i++ )
   {
      // now match the field name
      if (arr[i].innerHTML.indexOf(FieldName) > 0)
      {         return arr[i];      }
   }
}

function hideFields() {

   var control = findacontrol("Influence");
   control.parentNode.parentNode.style.display="none";
   control = findacontrol("Experience");
   control.parentNode.parentNode.style.display="none";
 
}
</script>

So just a couple of basics before we start.

• My portal is located at http://portal.abc.local
• I have a team site (standalone site collection) located at http://portal.abc.local/sites/hr

If I wanted to see a list of all of the site collections below my portal I can do that. The easy, out of the box way is to use stsadm.exe –o enumsites –url http://portal.abc.local

You will also notice from the screen shot that stsadm gives us more details in this version. ContentDatabase, StorageUsedMB, StorageWarningMB, and StorageMaxMB are all new pieces of information that could be handy in a pinch.

Anyway, back to the task at hand. How are we going to move HR to be part of the portal site collection? How about using stsadm.exe –o export

From the screen shot we can see at a minimum we will need to use the –url and –fliename options. So we probably want to run stsadm –o export –url http://portal.abc.local/sites/hr -filename HRsite.bak

Depending on the size of your site collection this command may run for several minutes. Once it finishes you will get a message saying Operation Completed Successful. Now we need to figure out how to get the site collection back in. To do this let's look at the command stsadm –o import

From this screen shot we can now see that we just need to do is import our previous file to a url inside our portal site collection. Something like stsadm –o import –url http://portal.abc.local/HR -filename HRsite.bak

Once again you should get a Operation Completed Successfully message. If you did then you should now be able to browse to http://portal.abc.local/sites/hr. Now don't forget to also go back and manually deleted your old site collection http://portal.abc.local/sites/hr once you are sure you have successfully moved everything. I will leave how to delete to you. It always scares me to give out instructions on deleting things because you never know who might only half way read this article and mindlessly delete something on accident. It happens!

Once you finish all of this moving around you will need to do a little navigation cleanup but nothing we can't do through site settings these days.

Shane SharePoint Help

Notes

I would just suggest that people make note of the -includeusersecurity option for both the export and import. Definitely save some headaches.

To determine whether the Stsadm.exe command-line tool was run successfully, review the Unified Logging Service (ULS) files that are located in the following folder:

"1.  After you have installed SharePoint, go under Operations, and Services on the Server.

2.  Under there, start up Office SharePoint Server Search. If you get an Error when doing this the most likly cuase is that you have to prefix the Domain in front of all user names ie

ML234APPS\Admin etc

3.  Next, setup Shared Services for that farm.

4. Go to the Shared Services Administration website, and under there go to “Search Settings” under “Search”.

5. Under Search Settings -> Manage Content sources and Crawl Schedules. You should see a “Local Office SharePoint Server sites” setup for ya. You’d think this would do it – but no.

6. Click on that link and setup a schedule for “Full Crawl” and “Incremental Crawl”. If you want – start up a full crawl after you are done setting up this schedule.

7. You can specify other search engine criterion here – URLs to exclude in search results, various rules on following links/domains etc., the content access account (make sure this isn’t administrator – and you would have set this up anyway when you setup SharePoint server search in item #2), file types etc.

That’s it. Your search is ready to rock’n’roll. Go to your site – issue a search; should work now. " From a blog at http://blah.winsmarts.com/2006-11-Implementing_search_on_a_Sharepoint_2007_installation.aspx#feedback

Using SharePoint Central Administration Web site SharePoint HTML Site Settings admin pages or IIS Manager, on the web sites properties HTTP Headers tab, virtual servers once extended will show the following version numbers: 
    MOSS 2007¹ or WSS 3.0 Cumulative update (KB956056 & KB956057)  12.0.0.6327
    MOSS 2007¹ or WSS 3.0 Infrastructure Update (KB951695 & KB951297)  12.0.0.6318
    MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB948945)      12.0.0.6303
    MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB941274)      12.0.0.6301
    MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB941422)      12.0.0.6300
    MOSS 2007¹ or WSS 3.0 SP1                                        12.0.0.6219
    MOSS 2007¹ or WSS 3.0 October public update               12.0.0.6039 
    MOSS 2007¹ or WSS 3.0 August 24, 2007 hotfix package 12.0.0.6036 
    MOSS 2007¹ or WSS 3.0 RTM                                        12.0.0.4518 
    MOSS 2007¹ or WSS 3.0 Beta 2 TR:                               12.0.0.4407 
    MOSS 2007¹ or WSS 3.0 Beta 2:                                    12.0.0.4017 
    Office 12 (PDC image - pre-beta):      12.0.0.3111 (This version of Office does not have a support link in the Add/Remove programs dialog box).

¹To confirm that a particular service pack is install on SharePoint Server you must either check the version numbers of specific dlls as specified in the related Microsoft Knowledge Based article or select the Show Updates check box in Add and Remove Programs.

    WSS 2.0 SP3                                    6.0.2.8165 
    WSS 2.0 SP2 KB900929 + KB924881 6.0.2.8117 
    WSS 2.0 SP2 rollup KB900929           6.0.2.8000
    WSS 2.0 SP2                                    6.0.2.6568
    WSS 2.0 SP2 Beta = R2:                   6.0.2.6551 
    WSS 2.0 SP1 + KB887981                6.0.2.6411
    WSS 2.0 SP1:                                  6.0.2.6361 
    WSS 2.0 Unservice packed:               6.0.2.5530

To confirm that service packs are installed, especially with SharePoint Server 2007, goto Control Panel -> Add and Remove Programs
Select the product and then click: Click here for support. The versions will
be displayed as follows:

See David Hunter's blog post, "SharePoint 2007 Versions ", to find the version number directly from a SharePoint database.

Thanks to Matthew McDermott and Kenneth Searles for the update on the version related to the hotfix KB887981

Note: If you have a version number starting with 10, then it is either SharePoint Team Services (SPTS) or SharePoint Portal 2001 (SPS 2001).

• SPTS, 10.0.2627.01 is the version with no service packs. In the Administrative Tools menu, you will see a link to Microsoft SharePoint Administrator. This will display a web page, where you can see the version number of the virtual server(s), e.g., 5.0.2.2623. The ISAPI filter is fpexedll.dll.
• For SPS 2001, 10.145.4629 is the version number with no service packs. There will be no ISAPI filter, and from the Administrative Tools menu you will see a link to SharePoint Portal Server Administrator which launches a mmc snap-in.