# Windows Server 2016 non-domain server, Ansible setup module issue

**URL:** <https://forum.ansible.com/t/windows-server-2016-non-domain-server-ansible-setup-module-issue/26059>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [November 17, 2017, 9:32am UTC](https://forum.ansible.com/t/windows-server-2016-non-domain-server-ansible-setup-module-issue/26059 "2017-11-17T09:32:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Fennemore](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@Mike\_Fennemore](https://forum.ansible.com/u/Mike_Fennemore)\
**Post date:** [November 17, 2017, 9:32am UTC](https://forum.ansible.com/t/windows-server-2016-non-domain-server-ansible-setup-module-issue/26059/1 "2017-11-17T09:32:52Z")

</div>

Ansible: 2.1.0.0  
Ansible Control Server: Centos 7.4  
Target: Windows Server 2016

On running the playbook it fails during the setup module. I have tested locally on the machine for the property in question and it is present.  
What is the cause?

TASK [setup] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Friday 17 November 2017 10:23:50 +0100 (0:00:00.054) 0:00:00.054 \*\*\*\*\*\*\*  
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
fatal: [server]: FAILED! =\> {“changed”: false, “failed”: true, “msg”: “The property ‘TotalPhysicalMemory’ cannot be found on this object. Verify that the property exists.”}

---

<div class="post-metadata">

**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:** [November 17, 2017, 1:17pm UTC](https://forum.ansible.com/t/windows-server-2016-non-domain-server-ansible-setup-module-issue/26059/2 "2017-11-17T13:17:36Z")

</div>

2.1 is 3 releases old and is no longer supported by Ansible. There has also been massive improvements and bug fixes for Windows since then and I would highly recommend you upgrade to at least 2.3 and try again.

I don’t know why it failed but unless you can verify it is still happening on the latest version there is not too much we can do for you.