Powershell scripts won't run on start up due to execution policy about windows-imaging-tools HOT 13 CLOSED

I've shoot the same bug today creating a windows 2012 r2 image on a Windows 8.1
The only warning I have is
WARNING: The installed version of DISM is older than the Windows image

Any help would be much appreciated

from windows-imaging-tools.

@adominus I was able to change to "Bypass" and get the scripts to run on FirstLogin/Login without error. "Unrestricted" will solve the "signed" error, but then throws an "UnauthorizedAccess" error, instead. Make sure to exit and relaunch your Powershell session (or reload the WinImageBuilder module) when building the image to pick up the new changes. (I sheepishly admit that I wasted a bunch of time yesterday tearing my hair out during troubleshooting because none of my code changes were being picked up.)

from windows-imaging-tools.

Same issue here as well, thanks for pointing out the "Bypass" option, it helped me get one step further

from windows-imaging-tools.

@tomcsanyid Glad I was able to help at least one person! ;-)

from windows-imaging-tools.

@Jbossalini thanks a lot. Sorry to hijack this thread, but you might have tackled this issue as well, and I have only this way to ask you: after I prepared my image (changing the XML did the trick) it now boots fine, has the default Cloudbase-Init Admin user etc. but I can't connect to the machine via RDP, so I only have the console in Horizon. Another machine I kind of hand-crafted together previously (running eg. cloudbase-init via hand) has RDP running by default, and I can connect to it easily.

from windows-imaging-tools.

@tomcsanyid Make sure you configure the firewall in Windows to allow RDP connections from Remote Address and, of course, enable the RDP port (TCP and UDP) in a Security Group in your Openstack tenant. Both Windows and Openstack block the port by default. HTH

from windows-imaging-tools.

@Jbossalini and @adominus
Thanks a lot, I have some good new for you, I talked to Gabriel :

1. The original problem could be solved by running unblock-file on all the files (or if you have the repo's ZIP file it is enough to run it on the ZIP file). For more info check:
   https://technet.microsoft.com/en-us/library/hh849924.aspx
2. My problem was related to not having port 3389 (RDP) in my Security Group settings allowed. After enabling it RDP started to work.

from windows-imaging-tools.

@tomcsanyid So does that mean we don't need to use "Bypass" anymore?

from windows-imaging-tools.

Yes. I need to try it out yet though, but I think yes. I'll get back to this on Monday.

from windows-imaging-tools.

Issue fixed by:
#32

from windows-imaging-tools.

Sorry to reopen a old ticket but I am having the same issue as @Jbossalini on Oct 2, 2015. Changing the setting in unattended.xml to bypass worked for me. I first tried Unrestricted and got the "Unauthorizedaccess" error.

This was during building a win10 enterprise image.

from windows-imaging-tools.

https://github.com/cloudbase/windows-openstack-imaging-tools/blob/master/UnattendTemplate.xml#L180 @swackhamer this is the code you changed?

from windows-imaging-tools.

Closing the issue, as there is no activity in the last months.

from windows-imaging-tools.