Creating Quota on other server

This topic contains 0 replies, has 1 voice, and was last updated by Profile photo of Forums Archives Forums Archives 5 years, 4 months ago.

  • Author
    Posts
  • #6276

    by BassieBas at 2013-02-15 02:18:27

    Hey guys,

    My script for making a new client in Win2008R2 is ready:
    – OU
    – Groups
    – Users with RDP paths
    – GPO with link
    – Folders with ACL settings

    The only problem that i have is with creating a new hard quota. We have 2 servers:
    – AD, GPO
    – Data (FRSM and shared folders)

    Right now, the quota is being created on the first server (AD, GPO), but i have to create it on the second server (Data).
    I run the script on the first server, how do i do this?

    In forward, many thanx!

    by DonJ at 2013-02-15 12:46:54

    What command are you using to create the quota? Does the second server have Remoting enabled?

    by Infradeploy at 2013-02-16 15:55:57

    dirquota quota add /path:d:\scratch /limit:50mb /remote:Dataserver

    by DonJ at 2013-02-17 12:54:26

    Try using a UNC path: \\server\d$\folder\folder\folder for the path. Or, if Remoting is enabled on the remote machine, you can send this command to the remote machine by using Invoke-Command. Those are probably your two best options.

    by BassieBas at 2013-02-18 01:28:25

    These are the commands to create a new quota.

    # Quota configureren
    $quotasize = 250
    $limit = 1024 * 1024 * $quotasize * $Aantal
    $fqtm = New-Object -com Fsrm.FsrmQuotaManager
    $quota = $fqtm.CreateQuota("\\dataserver\$Bedrijfsnaam")
    $quota.ApplyTemplate("hard quota")
    $quota.QuotaLimit = $limit
    $quota.Description = "$Bedrijfsnaam $aantal x Werkplek basis + $limit"
    $quota.Commit()

    With Remoting enabled you mean Remote Desktop Connection? Because that is working.
    As you can see, i already use a UNC Path so i also should use the Remoting command?

You must be logged in to reply to this topic.