I'm sure you can do the same thing in Powershell, but for those of us who
haven't revamped everything yet, rmtshare will provide what you need. I have a
scheduled task that does this for all of our file servers on a daily basis. I
believe that was actually part of one of the resource kits as I recall.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Michael Leone
Sent: Thursday, August 07, 2014 2:57 PM
To: [email protected]
Subject: Re: [powershell] Saving share permissions, and re-applying them
On Thu, Aug 7, 2014 at 2:45 PM, Kennedy, Jim <[email protected]>
wrote:
> Two step it.
>
> 1) Your backup system handles the NTFS perms during the restore.
There will be no restore, as there is no backup. As I said, the replicated LUN
will be mounted at the DR site on a replacement server.
(well, I mean, yes, we backup. But there's no way we am doing a 2TB+ restored
of 3M+ files. Not in any reasonable amount of time, anyway.
Hence the DR hotsite, and the replicated LUNs of the SAN)
> 2) Grab the sharenames and share perms from lanmanserver\shares.
>
> http://support.microsoft.com/kb/125996
>
> After the registry import you can manually edit drive letters if they
> changes. Done it this way several times.
I will look into it. The drive letters won't change; we'll just change the
drive letter of the mounted volume, if we have to (and we shouldn't need to)
================================================
Did you know you can also post and find answers on PowerShell in the forums?
http://www.myitforum.com/forums/default.asp?catApp=1
================================================
Did you know you can also post and find answers on PowerShell in the forums?
http://www.myitforum.com/forums/default.asp?catApp=1
