none
FIM2010 homeDrive provisioning in AD RRS feed

  • Question

  • Hi,

    I am trying to provision or create homedrives for users in AD. Is it fine, if I populate "homeDrive" and "homeDiectory" attributes in AD.

    In AD if we add these attributes, homedrives are created. Will the same work, if we populate these attributes from FIM.

    If not, what other options do I have ?

    Regards

    Sai

    Thursday, October 18, 2012 1:30 PM

Answers

  • You can populate those attribute but it will not automatically create the folder and set permissions.  When using ADUC and you populate those attributes from the gui, it will run a process to create them automatically.

    I use a powershell activity in a workflow to create home directories and set permissions when a user is created.  Others on these forums that know more than I have setup MAs for home directories.  My approach may not be preferred by some here but my PS scripts are getting the job done.

    Kirk

    Thursday, October 18, 2012 10:52 PM

All replies

  • You can populate those attribute but it will not automatically create the folder and set permissions.  When using ADUC and you populate those attributes from the gui, it will run a process to create them automatically.

    I use a powershell activity in a workflow to create home directories and set permissions when a user is created.  Others on these forums that know more than I have setup MAs for home directories.  My approach may not be preferred by some here but my PS scripts are getting the job done.

    Kirk

    Thursday, October 18, 2012 10:52 PM
  • Kirk,

    Thanks for your response. Will take the same approach.

    Regards

    Sai

    Thursday, October 18, 2012 11:19 PM
  • Hi,

    Alternatively you could take a look at Søren Granfeldt's or Omada's Home Folder MA?

    cheers

    Friday, October 19, 2012 12:11 AM
  • I know everyone likes PowerShell and workflow activities in the FIM Portal these days, but I've been using an XMA based on Carol Wapshere's example and probably won't replace it any time soon even as we upgrade from ILM to FIM.  It's an option, and one available even if you are only using the FIM sync engine and not the service/portal.

    Chris

    Monday, October 29, 2012 6:24 PM
  • I like the ideas of keeping this in MA's. Personally I use my own PowerShell MA (http://blog.goverco.com/p/powershell-management-agent.html) for this.

    Keep in mind that the XMA framework is now deprecated and you'll need to work towards a solution built on the ECMA2 or using workflows as suggested.

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

    Monday, October 29, 2012 8:49 PM