Duncan
Sat May 10 16:57:50 PDT 2008
Thanks for the info. There's plenty of space on the drive, my client's
problem is their *backup* - I don't want to backup WSUS, it's 17Gb or so
that just (IMO) doesn't need to be a part of the backup.
--
Duncan
In article <e#XbjyrsIHA.4076@TK2MSFTNGP06.phx.gbl>, "Henrik \(Hear\)"
<henrik-at-hotmail-com> says...
> Hi Duncan,
>
> heres a bunch of resources for you to use when space is running ut.
>
> How to Move Small Business Server 2000 Company and Users Shared Folders
>
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;329640
>
>
>
> Moving Data Folders for Windows Small Business Server 2003
>
>
http://www.microsoft.com/technet/prodtechnol/sbs/2003/maintain/movedata.mspx
>
>
>
> How to move Exchange databases and logs in Exchange Server 2003
>
>
http://support.microsoft.com/kb/821915
>
>
>
> How to Move the Client Programs Folder to Another Location in Windows Small
> Business Server 2003
>
>
http://support.microsoft.com/?scid=kb;en-us;830254
>
>
>
> How to Move the Windows Default Paging File and Print Spooler to a Different
> Hard Disk
>
>
http://support.microsoft.com/default.aspx/kb/314105
>
>
>
> Also: Look at where the ISA logs are kept
>
>
>
> You can move the C:\windows\uninstall$ folders off your system root, but you
>
> may want to keep them in case you have to move them back.
>
>
>
> Remove any folders or files under the c:\documents and settings\user
>
> name\local settings\temp folders.
>
>
>
> If Monitoring is enabled it can create a file that could be large. Run
>
> through the wizard again to flush out the gooey stuff..
>
>
>
> Delete logs older than "date of your choice" from the system32 folder.
>
> Likewise the logs and reports from the ISA folder.
>
>
>
> Search for and delete old dmp files.
>
>
>
> You can move the page file to another partition. The only downside is that
>
> if you get a "blue screen" you will not get a full memory dump, and since
>
> only MS can read them anyway, I don't see that it matters much.
>
>
>
> You may gain some usable space and increase system performance in Windows
>
> Server 2003 by moving the printer spool files to a different drive than the
>
> one that holds the operating system. Note that this should be a different
>
> spindle, but a different partition will help the OS a bit also.
>
>
>
> By default, Windows Server 2003 places the printer spool folder at
>
> %systemroot%\System32\Spool\Printers. However, you can potentially increase
>
> system performance by moving the printer spool files to a different drive
>
> than the one that holds the operating system.
>
>
>
>
>
> Computers frequently access system files, so moving the printer files to a
>
> different location allows faster access to those files. The drive won't have
>
> to try to service requests simultaneously.
>
>
>
> To change the location for the printer spooler files, follow these steps:
>
>
>
> 1. Go to Start | Printers And Faxes.
>
> 2. From the File menu, select Server Properties.
>
> 3. On the Advanced tab, enter the location where you would like to spool
>
> print jobs. If the location doesn't exist, this process will create it for
>
> you. Make sure the new location has sufficient disk space to handle large
>
> print jobs.
>
> 4. Stop and restart the printer spooler service, or reboot the server.
>
>
>
> Regards
>
>
>
> Henrik, MCP-SBS
>
>
>
> "Duncan McC" <hard@work.ok> skrev i meddelandet
> news:MPG.228e5e98d8c7c1b998996b@news.microsoft.com...
> > Thanks for that info Philip - I need to do the same for a client too.
> >
> > I'd also like to move the internal windows database too - is that a
> > possibility?
> >
> > I was just going to disconnect the db via SQL Management Studio, move
> > the files over to the new location, and join them up again.
> >
> > --
> > Duncan
> >
> > In article <DEF333E0-5EB4-4321-8533-C00AF53DDC05@microsoft.com>,
> > groups@ootbx.ca.NOSPAM says...
> >> TechNet document:
> >>
http://technet.microsoft.com/en-us/library/bb245839.aspx
> >>
> >> Changing the location where you store update files locally
> >> You might need to change the location where WSUS stores updates locally.
> >> This might be required if the disk becomes full and there is no longer
> >> any
> >> room for new updates. You might also have to do this if the disk where
> >> updates are stored fails and the replacement disk uses a new drive
> >> letter.
> >>
> >> You accomplish this move with the movecontent command of WSUSutil.exe, a
> >> command-line tool that is copied to the file system of the WSUS server
> >> during WSUS Setup. By default, Setup copies WSUSutil.exe to the following
> >> location:
> >> WSUSInstallationDrive:\Program Files\Microsoft Windows Server Update
> >> Services\Tools\
> >>
> >> You must be a member of the local Administrators group on the WSUS server
> >> to
> >> use the movecontent command of WSUSutil.exe. These operations can only be
> >> run from the WSUS server itself, which must be a 32-bit platform.
> >>
> >> You must create the new path for local WSUS update storage prior to using
> >> WSUSutil.exe. The movecontent command takes an optional -skipcopy
> >> parameter.
> >> The -skipcopy parameter enables you to change the location of local WSUS
> >> update storage without copying any files. For more information about
> >> WSUSutil.exe, see Deploying Microsoft Windows Server Update Services.
> >>
> >> To change the location of local WSUS update storage
> >>
> >> Click Start, and then click Run.
> >> In the Open box, type cmd, and then click OK.
> >> At the command prompt, navigate to the directory that contains
> >> WSUSutil.exe.
> >> Type the following, and then press ENTER:
> >> wsusutil.exe movecontent contentpath logfile [-skipcopy]
> >> For example, type:
> >> wsusutil.exe movecontent D:\WSUS1\ D:\move.log
> >> where D:\WSUS1 is the new path for local WSUS update storage, and
> >> D:\move.log is the path to the log file.
> >>
> >>
> >
>
>
>