Posts Tagged: sysadmin

default — No Comments
4
Feb 10

Increasing the maximum size of list templates

This is “Copy-Paste” post from here, but it is so useful for me so I don’t want to loose it and my blog is the safest place for this info.

Post descibes MOSS 2007 and WSS 3.0, but it works for WSS 2.0 and SPS 2003 too.

Saving a list as a template is an easy way of transferring data from one place to another in SharePoint. By default, however, the maximum size of list templates in WSS 3.0 and MOSS 2007 is 10MB.

If you try to save the list as a template that is larger than this you will get the following error:

The list is too large to save as a template. The size of a template cannot exceed 10485760 bytes.

To increase the maximum size, simply run the following stsadm command (from the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN directory) replacing the propertyvalue to the new maximum size (in bytes):

stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 50000000

Points to note:

  • The propertyvalue parameter is in bytes, so the example above will increase the maximum size to approx 50MB.
  • There is a hard limit of 500MB so the value must be less than 524288000 or you will get an error when saving the list as a template.
  • The above increases the maximum size of both site and list templates.
default — No Comments
21
Jan 10

What to do if WebDAV in your Windows7 is too slow

Go to IE settings and disable “Automatically detect settings”. Point. :-\

default — No Comments
30
Nov 09

How to edit other user’s NTUSER.DAT

What if you need to edit some user’s registry and it is not listed in HKEY_USERS? For example we have like 400 profiles on one of our servers and regedit shows only around 20 under HKEY_USERS. I’ve found solution on one of forums:

To modify each users entries:

1. Open regedit
2. Click on HKEY_USERS keyname
3. File | Load Hive
4. Select one of the Users ntuser.dat file
5. Give it a unique name for adding to HKEY_USERS
6. Open HKEY_USERS\[UNIQUE NAME]
7. Make modifications
8. Click on HKEY_USERS\[UNIQUE_NAME] keyname
9. File | Unload Hive
10. Do next user

Very awkward user interface, but it works.

default — No Comments
25
Nov 09

XenServer 5.0 and Windows 7

Today my colleague asked me to create VM on our XenServer 5.0 farm with Windows 7. I pulled my DVD with Windows 7 RC and tried to deploy it on VM, but it hanged on screen “Starting Windows”. I spent some time googling and found this:

A colleague recommended the following:

“1) XenServer 5.0: Due to a bug in the HyperV extensions, installing a Windows 7 OS on XenServer 5.0 server may result in a blue screen or get hung during initialization. In order to install Windows 7 images on a XenServer

5.0 machine, you will need to perform the following workaround:

$ xe vm-param-set uuid= platform:viridian=false
You can obtain the vmuuid by running the following command from your host: xe vm-list

2) XenServer Tools: the XenServer tools currently do not work on Windows 7. If you attempt to install them you will experience a blue screen! ”

Recommended command did the trick and I’m looking on Windows 7 installation right now.

default — No Comments
11
Nov 09

Microsoft Sharepoint 2003 subsite migration

From the day one of my experience with SPS 2003 I had one big problem – migration of subsites from one place to another. And here is solution that works.

“there’s a nice simple way to do this.” It is a 3 step process

… assuming you have Front Page 2003 and you are not trying to move something from under a “My Site”.

1) Open front page 2003 and point it to the site that you wish to backup and move (we’ll call this your “source” site).

1a.) Open FrontPage: File> Open Site (you will be looking at a list of folders and templates with a deafult.aspx somewhere in the list).
1b.) Tools> Server> Backup Web Site
1c.) You can choose to simply backup this site, or to backup all sub-sites as well (this backup does include content as well)

2) On the destination server you need to go create a site with the same name as your source site.

2a.) Navigate to the place on your portal where you want to create this site
2b.) Create a new site, but DO NOT apply a template. This site must have the same name as the original source site.
2c.) When you are prompted for the template simply close the browser.

3) Open up front page 2003 and this time point it at the new site you just created on your destination box. Then restore the site (you did save it someplace convenient, right?)

3a.) Open FrontPage: File> Open Site (this will look empty compared to the site you saved just a few minutes ago)
3b.) Tools> Server> Restore Web Site (You will need that backup file here)
3c.) Ta Da! You are done!

Note: This does NOT make a full fidelity backup. Which means that any security that you had set up for the source file does not exist after importing to the new destination. You will have to re-setup security. Other than that, it’s good to go.

If you want a full fidelity backup, that is a lot more complex and requires a lot of command-line processing. Not eactly “a nice simple [method]”

via

← Older Entries