User Logon scripts in PowerShell doesn't work on Windows Server older than 2019

By -

I've created a simple PowerShell script which writes a few text data into CSV file every time when the user logon and logoff to the servers (based on Windows Server 2008, 2012, 2016 and 2019). E.g. Get-Date | Export-CSV -Path \\server.domain.local\Folder\file.csv.
It has been set to the User Configuration GPO Policy for Logon and Logoff PowerShell scripts. Scripts were placed on the SYSVOL (Policy folder) and for test as well on the NETLOGON folder (GPO's placed there use PowerShell Bypass policy by default). Authenticated Users have Read and Read& Execute permissions on the SYSVOL/NETLOGON folders where the scrips are located and on the scripts itself same permissions exists. Authenticated Users have the write permissions on the target CSV file and folder. When standard, administrator and domain admin users logs in to the Windows Server 2019 both Logon and Logoff scripts works well and writes the data into the CSV file. For Windows Server 2008 R2, 2012 R2 and 2016 it doesn't work. Any ideas what the issue could be?

I've added Policy Bypass in the PowerShell scripts directly - but that haven't change anything. I've added Policy Bypass as PowerShell script in GPO policy as a execution parameter but still no change. No error messages in the servers or DC's event logs. Scripts have not been digitally signed yet to not complicated the situation.



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more