Re: NTFS Compression
- From: "Mitch Tulloch" <info@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 31 Jul 2005 12:08:59 -0500
You're welcome and good luck!
--
Cheers,
Mitch Tulloch
[MVP--Windows Server]
http://itreader.net
"Tom Horsley" <tom-remove-horsley@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:OU4SPr$kFHA.3828@xxxxxxxxxxxxxxxxxxxxxxx
> Mitch,
>
> Thanks for your thoughts. I like the idea of the batch file but in this
> particular case it isn't an option. The server is old and due for
> replacment; disc space is low and the available free space is less than
> would be required to uncompress all the folders. I'm not sure what would
> happen if one of the users was to 'untick' the box. Hence my frustration.
>
> First thing was to add some disc space (a pair of mirrored 36Gb discs to
> take some of the pressure of their RAID 5) The plan is to move some of the
> folders onto it and uncompress all folders. At that stage I may apply your
> excellent idea.
>
> User disciplne is difficult at this site (I suspect that my best option is
> for them to become Ex Clients) The worst offenders seem to be the senior
> management - one guy managed to open up a quaratined virus laden e-mail
> "because he'd never seen a virus before!".
>
> If it wasn't for the users, computers would be great.
>
> Thanks again.
>
> PS I still can't believe that Microsoft designed this facility for users
> without giving administrators the power of veto. I'ts either a big mistake
> or their designers need to spend more time in the real world.
>
> Tom Horsley
>
> "Mitch Tulloch" <info@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:OzP6er7jFHA.3568@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi Tom, I agree there *should* be some way (maybe using Group Policy) to
>> disable compression on NTFS volumes, but unfortunately there isn't.
>> Here's
> a
>> workaround that might help you though:
>>
>> 1. Create a batch file using the compact.exe command to uncompress all
> files
>> and folders on the data volume on your server e.g.:
>>
>> @echo off
>> C:\Windows\system32\compact /u /i /f /s:z:\
>>
>> where z: is the data volume on the server.
>>
>> 2. Save this as C:\batch\uncomp.bat or something similar.
>>
>> 3. Use Scheduled Tasks to schedule your batch file to run during off
> hourse
>> e.g. 4 a.m.
>>
>> That way if any user *does* compress files or folders on your file server
>> volume, these files and folders will be automatically uncompressed each
>> night, and users will probably soon get the idea that there's no point in
>> them compressing stuff on your file server ;-)
>>
>> However, I strongly suggest you consider finding ways to get those users
> who
>> are "undisciplined" to comply to your policies e.g. add a "Do not
>> compress
>> stuff on the file server" policy to your user guide, provide escalating
>> consequences for those who ignore this policy, educate users concerning
> your
>> policies, and enforce the consequences of non-compliance consistently and
>> fairly. Half of network administration/security is about getting users to
>> understand and comply with policies and procedures, and this is important
>> because there's not always a simple and cheap technical solution for
>> everything the administrator has to deal with. Of course, an essential
> part
>> of making policies effective is to have the support of management and the
>> cooperation of Human Resources. Just my two cents ;-)
>>
>> --
>> Cheers,
>> Mitch Tulloch
>> [MVP--Windows Server]
>> http://itreader.net
>>
>>
>>
>> "Tom Horsley" <tom-remove-horsley@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>> wrote
>> in message news:ObmBWDuhFHA.3164@xxxxxxxxxxxxxxxxxxxxxxx
>> > I've been investigating this further and cannot believe that as admin
>> > of
>> > the
>> > system I have no way of preventing the use of compression.
>> >
>> > Olaf said: "Usually any user who has write permissions for a folder can
>> > also
>> > alter the compression settings."
>> >
>> > I don't understand the logic of that on a network. Why should this user
> be
>> > able to degrade the network performance of a system.
>> >
>> > To describe the problem more clearly: Xp clients need to map shared
>> > folders
>> > from the server as drives. But as soon as this is done they are able to
>> > access the properties of this mapped drive & compress it. Or uncompress
> it
>> > if someone else has compressed it etc...
>> >
>> > I should perhaps mention that these are not particularly well
> disciplined
>> > users.
>> >
>> > Surely whether or not a server shared folder is compressed is a
>> > decision
>> > for
>> > the administrator, not users. Is this unreasonable?
>> >
>> > Question: How do I stop them? (Broken fingers aren't an option
>> > unfortunately)
>> >
>> > --
>> > Regards,
>> >
>> > Tom Horsley
>> >
>> >
>> >
>>
>>
>
>
.
- Prev by Date: Re: Recommended AMD motherboard for 32bit Windows SBS 2003
- Next by Date: Re: Implementing 3 Dual boards and NIC's
- Previous by thread: Recommended AMD motherboard for 32bit Windows SBS 2003
- Next by thread: Re: LDAP
- Index(es):
Relevant Pages
|
