Effortless chef-client on windows conflicting with legacy client

[sam1el]

Description

When loading effortless service on windows, the effortless client is colliding with configs for the legacy chef-client on the base OS.

Scaffolding Version

Using Stable version 0.19.0 for windows

Platform Version

• Microsoft windows 2012r2
• revision windows 6.3.9600

Replication Case

Removed older chef-client and path information and all effortless packages function as expected on test machines. The remaining 5 machines have the same settings that were removed from the test box

Legacy client version is

• Stable version 13.2.20

System environment PATH information

C:\Program Files (x86)\Tanium\Tanium Client\python27\lib\site-packages\pywin32_system32;c:\Program Files\avs\bin;c:\Program Files\avs\bin32;C:\Program Files\EMC NetWorker\nsr\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft Network Monitor 3\;C:\Program Files (x86)\CA\SC\Csam\SockAdapter\bin;C:\Program Files\java\jre7\bin;C:\opscode\chef\bin\;C:\opscode\inspec\bin\;c:\opscode\push-jobs-client\bin;C:\habitat\

Client.rb

chef_server_url  "https://hidden.net/organizations/hidden_am2"
validation_client_name 'hidden_am2-validator'
validation_key 'c:\chef\hidden_am2-validator.pem'
ssl_verify_mode :verify_none
rubygems_url 'http://artifactory-hidden.net/artifactory/api/gems/rubygems' 
node_name 'somenode.hidden.net' 

Build or Run Output

Build succeeds.