Re: Exchange Move Issues?

I'm a bit confused on what permissions to assign for SBS, see Note below..

6. When you finish moving the databases, remount the databases manually.
You can move the log files and database files to any folder that you want to
create. When you move logs and database files, you may want to create the
Exchsrvr\Mdbdata file structure for consistency reasons, but you are not
obligated to do so.

You must grant the following default permissions to the new Mdbdata folder
that contains the log files and database files: • Administrators: Full
Control
• Authenticated Users: Read and Execute, List Folder Contents, Read
• Creator Owner: None
• Server Operators: Modify, Read and Execute, List Folder Contents, Read,
Write
• System: Full Control
Note Only assign permissions to the Server Operators group if the Exchange
server is a domain controller. Otherwise, assign permissions to the Power
Users group. Only domain controllers should have permissions to the built-in
Server Operators group. Stand-alone and member servers should have
permissions to the built-in Power Users group.

You may also have to grant the following permissions to the root drive that
contains the new Mdbdata folder: • System: Full Control


"Larry Struckmeyer" wrote:

Ok, since I seem to post that list with some frequency, I have added the
notes about checking the AV scans and the dump file.

Good catches SG and Jon-Alfred.

--
Larry


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:ugjaw3mfIHA.4140@xxxxxxxxxxxxxxxxxxxxxxx
The only aspect of this I disagree with, strongly, is moving the default
paging file.

If you move the default paging file off your OS partition you lose the
ability to get full dumps. We all hope such is never necessary but a fact
of life is they are, hopefully rarely.

Everyone should have room on their OS partition for a RAM+20MB (actually
it's +~12MB) paging file, even if full dumps are not normally enabled. You
never know when you might want to enable them.

ME. 'Check that full dumps are enabled' is on my install checklist.

"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message
news:erkIMumfIHA.4196@xxxxxxxxxxxxxxxxxxxxxxx
Hello:
Here is some additional space saving/making tips accumulated from this
newsgroup.

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 Small Business Server 2000 Company and Users Shared Folders
<http://support.microsoft.com/default.aspx?scid=kb;en-us;329640>

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 if you have SBS Premium.

You can move the C:\windows\uninstall$ folders off your systemroot, but
you may want to keep them in case you have to move them back to uninstall
something in the future. I have only ever had to do this once, and it
was not an SBS.

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.

--
Larry


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:upMZhclfIHA.5164@xxxxxxxxxxxxxxxxxxxxxxx
good catch, though many server and exchange aware AV's will do this
automatically it is still worth a mention.

"Jon-Alfred Smith" <jonsmi@xxxxxxxxxxxxxxxx> wrote in message
news:icprs3d74mk6bupcpch3dthm0gldl948uu@xxxxxxxxxx
On Wed, 5 Mar 2008 10:52:38 +1100, "SuperGumby [SBS MVP]"
<not@xxxxxxxxxxx> wrote:

The Exchange database can be (and should be) moved to another partition
from
within Exchange System manager. You are best off first creating the
folder,
say, d:\mdbdata.

The process takes the stores offline, moves the files, and remounts it.
No
change to WSUS is required. I'm not sure whether you then need to run
the
backup wiz, may as well for good measure.

Exclude file-based antivirus scanning on the new folder
http://support.microsoft.com/kb/245822
http://support.microsoft.com/kb/328841

jas









.

Relevant Pages

  • RE: Windows 2003 Server - Everyone Group
    ... this folder only accessable by the users in the "special" group. ... Configure User and Group Access on an Intranet in Windows Server ... NTFS files system permissions control ... group that you want to set permissions for, click Check Names to verify the ...
    (microsoft.public.win2000.networking)
  • Re: Office Docs wont Open? and BU Drive not Recognized?
    ... Create a new Folder: ... On the server share... ... SHARING tab | Permissions | Share Permissions | Group or User Names ... If I copy the document to the local Client, the document opens ...
    (microsoft.public.windows.server.sbs)
  • Re: An NT Security Gotcha that looks like a Jet Security issue
    ... >people remotely via Windows Terminal Server. ... >code when it was run by a user that didn't have full permissions on ... There's a top-level DATA folder, ... >ApplicantsDB and Quickbooks. ...
    (comp.databases.ms-access)
  • Re: MS - Access Issues
    ... I don't see anything anywhere for NTFS folder permissions. ... Nor can it find the domain server. ... checked to bypass proxy server for local addresses. ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding a database to existing workgroup file
    ... > monitor the status of tables in the databases. ... RWOP (run with owner permissions) queries as the recordsources for all forms ... Users need read/write/create/delete permissions on the folder. ...
    (microsoft.public.access.security)