Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Creating tasks on windows 10 1709 remotely from linux RRS feed

 > 

  • General discussion

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Hi Team,

    I am working on an important task where i need to create tasks using task scheduler on windows 10 systems remotely from linux using opensource samba code on linux. Basically i have xml file where i will pass xml buffer in samba code and ultimately it will open a pipe with remote windows 10 system and will create the scheduled tasks on windows machine.

    Code is working for windows 10 1511 version but it not working for Windows 10 1709 & 1803 versions and it is returning error in samba code as NT code 0x80070005. So in this regards i would like to know what changes were done in windows 10 1709 & 1803 versions in Task Scheduler ? Are there any parameters newly introduced in 1709,1803 versions of windows 10 for task scheduler? Please let me know your response....

    Friday, April 20, 2018 3:58 PM

All replies

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    The error says "access denied". Security on 1709 has been increased. You will have to check the Windows logs for specific information.

    \_(ツ)_/

    Friday, April 20, 2018 4:03 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Thanks .. Can you please let me know what those windows logs you are referring?
    Friday, April 20, 2018 4:06 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    You will have to get someone familiar with Windows to help you.  YOu can also ask your Linux/Samba question in a Linux/Samba forum.

    Windows Event logs are a fundamental component of Windows.

    \_(ツ)_/

    Friday, April 20, 2018 4:29 PM
  • Discussion
    Sign in to vote
    1
    Sign in to vote

    Thanks for your response though not useful information in it. I already did enough research and dig all the windows event logs /system logs/security logs and checked all Local security options on windows 10 1709. I could not found out anything in them . As final step i approached these forums for help.

    Already posted questions on samba forum though..

    Friday, April 20, 2018 4:34 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    We have no idea what you are doing or how you are trying to do it so we cannot guess at which logs will contain the information.  Windows has more than 100 event logs.  All service errors will be in the log for the service where the error was detected.  "Samba"  is not a Windows service.

    You either need to work with someone trained in Windows or post in a Linux forum for your utility.

    YOU have not defined how you are accessing the Windows scheduler.  WMI, Registry, File System, WsMan, etc.

    \_(ツ)_/

    Friday, April 20, 2018 4:44 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Yes samba is not a windows service and it is opensource .. I know that. Same set of changes working for windows 10 1511 version and not working for 1709. So thought of finding what might be basic difference between two incase of task scheduler.

    I explained in my question about how iam creating tasks from samba. Let me explain:

    Samba will open a pipe with \\<windows 10 system>\IPC$ and later over SMB2 and DCERPC it will try to connect to windows 10 machine and exchange messages .Samba will send XML file (having details about task to be created and at what time to be created etc) to windows 10 via DCERPC protocol. The same is working for 1511 version but access denied for 1709. Attached screen shot of PCAP file ...Please have a look if you think you can understand it... I can ask more details if you really interested to understand and answer my question...

    Friday, April 20, 2018 4:56 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Sorry, but this is not the right forum for your question.

    This forum is for scripting questions.

    -- Bill Stewart [Bill_Stewart]

    Friday, April 20, 2018 5:04 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Can you please let me know what is the right forum to post ?
    Friday, April 20, 2018 5:06 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    So to describe this in non-pseudo technical terms.  You are using SMB to copy a file to a Windows share.  You are getting an "access denied" error. 

    Copying XML files to the scheduler has always been an issue and MS has apparently further blocked this for both security reasons and for system reliability reasons.  Each version of Windows continues to refine the security on system folders and resources.  Most of use have avoided the old early Window's technique of copying scheduler files to systems.

    In Windows 10 direct access from the network to this folder been limited.  I would suggest contacting the support group for Samba to see if they have a fix for this.  You can also just use remoting to import the  XML file into the scheduler.

    If you try to alter the system security on system folders it is likely the next patch or upgrade will just reset the security.  Unless specifically allowed users are not supposed to alter settings in the Windows system area.

    \_(ツ)_/

    Friday, April 20, 2018 5:08 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Can you please let me know what is the right forum to post ?

    You should always start closest to home and post in a Linux/Samba forum.

    \_(ツ)_/

    Friday, April 20, 2018 5:08 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Okay thanks for your response. But the confusing point is same piece of samba code working for windows 10 1511 version and not working for 1709. Not sure what might have changed in 1709 version. So thought of finding what might have changed in 1709.
    Friday, April 20, 2018 5:18 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Okay thanks for your response. But the confusing point is same piece of samba code working for windows 10 1511 version and not working for 1709. Not sure what might have changed in 1709 version. So thought of finding what might have changed in 1709.

    Which I answered in my first reply.

    \_(ツ)_/

    Friday, April 20, 2018 5:21 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    You are also trying to use the IPC$ share which has been more protected since Windows Vista.  As best I can remember this was more relaxed in XP/WS2003 and earlier.  This IPC$ share is just a handle to the IPC layer of the OS.  It needs very specific authentication which might be a problem for unix sockets or Samba.  Hence posting in the correct forum would be best.

    \_(ツ)_/

    Friday, April 20, 2018 5:27 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    I did some quick testing on 1709 and earlier.  The security on the tasks folders has not changed.  What has changed is that authentication is stricter and MS has droped support for some secure protocols.  This is also tru of earlier versions than 1709 and W10.  I suspect you are having issues with correct authentication with you Linux utilities.  I cannot reproduce you issue with Windows and remote access when correctly authenticated works as it always has.

    Assuming the issue is 1709 may be sending you down the wrong path.  Start by verifying that your Linux system can correctly authenticate on Windows with a correct Admin account.

    With Samba you should be able to just copy the file to the folder.  No need to use IPC$ OR ANY SOCKETS.

    \_(ツ)_/

    Friday, April 20, 2018 5:37 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Okay Thanks a lot for your inputs...
    Friday, April 20, 2018 6:05 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Can you please let me know what is the right forum to post ?

    Sorry, but this is also not the right forum to ask about where to post off-topic questions. You will need to use a search engine to find an appropriate place.

    -- Bill Stewart [Bill_Stewart]

    Friday, April 20, 2018 8:02 PM