Disable data access but maintaining print Q use ?

[thrapper]

Hi all,
Am working on Netware 3.x data migration to new W23K platform. We will temporarily need to maintain printing via the Netware print Q's but at the same time disable login (or otherwise prevent access to data) so that users can only update data that is in new migrated location. The Netware 3.x print Q's are on SYS: volume, all user and team data is on a seperate "DATA" volume (being migrated). If I just dismount DATA volume will users still be able to connect and use printing facilities (hosted on SYS)?
Is there a KB article to support this anywhere? If this is not feasible are there any alternative solutions?

Thanks in advance for responses.

Mark

 

[itsp1965]

Mark dismounting the volume is a bit drastic. Why don't use Syscon to remove access to the DATA volume for everyone.Disabling login will prevent access to the queues.

 

[thrapper]

Thanks itsp1965. Do you mean revoke rights for the group "Everyone" ? Must admit that seems a lot simpler. I think there are concerns of people inadvertantly getting back to Netware storage and updating files that have actually been migrated. Assumed dismounting the volume would actually make it impossible to map a drive to it, thus negating any risk. I'd just 'dismount DATA' at console and edit autoexec.ncf from 'mount all' to mount SYS and mount DATA (but latter remmed out)..... Thanks in advance, Mark

 

[itsp1965]

Mark it depends on how complex the security is setup for the volume. If in Syscon you have the Everyone group with rights to (R)ead and (F)ile Scan for the DATA vol then they can map directly to DATA and navigate down the folder path. If you remove this (and even access at lower levels like group and app folders -- depending on your setup), they are going to have to map specifically to the resource they have rights to.

But as you said if you want to guarantee no access to DATA well then you can dismount and rem it out of autoexec.ncf

 

[thrapper]

Thanks itsp1965
I think the security is quite complex with many groups having many mappings run from Windows domain controllers. That's why dismounting DATA volume seemed a reasonable option. If I go this way I ensure no access to data on that volume, if SYS is still mounted will users still be able to print?

Thanks, Mark

 

[itsp1965]

On a Netware 3.x server SYS is the only place where print qs can reside, so it is safe to say they will still be able to use the printing env while only SYS: is mounted

 

[thrapper]

Many thanks itsp1965
I'll let you know how I get on as the migration is happening soon.
Mark

 

[marvhuffaker]

If it was me, I'd disable access to the Windows system, upgrade the Novell system to NW6.5, migrate printing to NDPS/iPrint, and let the users access the data on the new server.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[thrapper]

Thanks Marvhuffaker
Unfortunately I don't have that luxury. We are migrating all our Netware servers to Win 2003 (not my idea!!). Data migrates first, printing in 'x' months. So we need to maintain printing after the data has migrated to new platform.

Thanks, Mark.