# Why is ConfigureRemotingForAnsible.ps1 not suitable for production? **URL:** \ **Category:** Ansible Project\ **Tags:** windows\ **Created:** [September 27, 2018, 12:26pm UTC](https://forum.ansible.com/t/why-is-configureremotingforansible-ps1-not-suitable-for-production/28661 "2018-09-27T12:26:10Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![swinickitom](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@swinickitom](https://forum.ansible.com/u/swinickitom)\ **Post date:** [September 27, 2018, 12:26pm UTC](https://forum.ansible.com/t/why-is-configureremotingforansible-ps1-not-suitable-for-production/28661/1 "2018-09-27T12:26:10Z")
The [ConfigureRemotingForAnsible.ps1](https://github.com/ansible/ansible/blob/devel/examples/scripts/ConfigureRemotingForAnsible.ps1) file to setup Windows hosts for Ansible is not suitable for production according to the documentation. Why is it not suitable for production and what can I tweak in the file to make it suitable for production? ---
**Author:** ![jborean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jborean/32/1525_2.png) [@jborean](https://forum.ansible.com/u/jborean)\ **Post date:** [September 27, 2018, 7:35pm UTC](https://forum.ansible.com/t/why-is-configureremotingforansible-ps1-not-suitable-for-production/28661/2 "2018-09-27T19:35:15Z")
Because it does a few things like enabling Basic auth and uses self signed certificates and usually globally allows WinRM traffic through. In a normal production environment you shouldn’t be using Basic auth, using a CA signed certificate and only allow WinRM traffic on the network profile you want. Unfortunately some of these changes we cannot modify as a lot of people rely on this behaviour and just pull straight from GitHub so we just put up a warning saying don’t use this directly in Production. Thanks Jordan