A few weeks ago we had an Windows XP box connected to an AS/400 network share mapped to drive
P://. Batch files could be run from a remote call command from the 400. The batch files were called with a user password none / none.
We had to take the Windows XP box off the network suddenly without planning or the ability to get a replacement set before having to take it offline.
In comes an Windows 10 box. Due to the AS/400 not being on the domain, I have to map drive
P:// with ./user and password. Everything is fine we have full control over folders and file, read, write, delete.
P:// is where the AS/400 dumps HTML files for converting to PDF and then spooled - using a command line call to a Qindows program. gain everything was working on the XP box - but now all of a sudden the Windows 10 box seems like it has not authority to the
The user on logged in through AD is an administrator on the machine.
I have tried creating a ps-drive through PowerShell. It says that the execution policy restricts the action from being completed. Tried using credentials to log into the ps-drive and I can't get the prompt to take a ./ for the domain.
Standard batch files - run manually have access to the share through the drive letter but when I try to run the batch files through scheduled tasks it doesn't run seeming like it doesn't have access to the drive all of a sudden.
I've created a system link - but can't seem to get PowerShell to be able call the system link.
Basically what I need to do is after the HTML is created kick a batch file to convert to PDF and print - in an automated way.
I am stuck not understanding the security role issues between PowerShell and the drive - and the task scheduler and the drive.