0

I just want to migrate from windows server 2012r2 to windows server 2016 or 2019, but I have the following problem with a service. If I query the service in 2012r2, everything works and I get Events in the event viewer. Events are like this one:

 A network share object was checked to see whether client can be granted desired access.
Subject:
    Security ID:        LABVM2012R2\Administrator
    Account Name:        Administrator
    Account Domain:        LABVM2012R2
    Logon ID:        0xF47C Network Information:    
    Object Type:        File
    Source Address:        10.0.2.156
    Source Port:        49216
Share Information:
    Share Name:        \\*\ias
    Share Path:        \??\C:\ias
    Relative Target Name:    Ipod\MASTER\GuardLog.ini Access Request Information:
    Access Mask:        0x2
    Accesses:        WriteData (or AddFile)
Access Check Results:
    WriteData (or AddFile):    Granted by    D:(A;;FA;;;WD) 

The path in the event is a network share inside the server, Accessed by a local administrator. I made same path and same files in the other 2019 and 2016 virtual machine. If I run them on windows 2019 or 2016 I get events like this one:

An attempt was made to change an account's password.

Subject:
    Security ID:        LAB2016\Administrator
    Account Name:        Administrator
    Account Domain:        LAB2016
    Logon ID:        0x1343C

Target Account:
    Security ID:        S-1-5-21-1306156681-3583148203-3419298570-0
    Account Name:        
    Account Domain:        LAB2016

Additional Information:
    Privileges        -

I am using the same local administrator in both virtualbox vm. The folder mentioned in the 2012r2 log is a local share in the server, I made the same folder in the 2016 and 2019 virtualbox.

The program on window 2016 and windows 2019 gives this error:

Service may not have administrator rights to this server

I am trying to figure out what changed in the local network authentication between 2012r2 and 2016 and why the program is not working there. Thank you if this rings a bell. I guess I would eventually have similar errors If I were running the program in windows 7 professional and in windows 10 professional.

Hoygen
  • 1
  • 2

0 Answers0