Merge pull request chef-cookbooks#245 from pratixha/pratiksha/windows…

…_unsupported_custom_path

Added docs for windows custom path

README.md

@@ -35,6 +35,10 @@ The PowerShell upgrade script then moves the current installation to a `chef.upg
 
 On Windows the only supported `post_install_action` is `kill` (the property will be forced to `kill` if given `exec` and platform is Windows) because the Chef Infra Client process must be terminated before the `Chef_upgrade` scheduled task starts in order to release all open file locks by the client, otherwise the upgrade will fail with file-in-use errors.
 
+Root installation path for chef-client in cookbooks/chef_client_updater/attributes/default.rb when a custom path is used.
+`default['chef_client_updater']['chef_install_path'] = 'CHEF_CLIENT_FOLDER_PATH'`
+Defaults to 'C:/opscode/chef' on Windows and '/opt/chef' for everything else.
+
 #### Running Chef Infra Client as a Scheduled Task
 
 If you run as a scheduled task, then this will work smoothly. The path to the newly installed Chef Infra Client will be the same and the scheduled task will launch it. Part of this resource's job on the next run is to make sure the staging directory with the older client is removed.