I began having an issue with my jamf enrollment for Windows around 07/07/16. Possibly around the time I upgraded from 9.91 to 9.92. I knew something was wrong but realized this morning that no Windows Computers were even checking in. I ran the jamf.exe manually with parameters and here is the error:
PS S:> C:WindowsTempjamf.exe recon -overrideJSS https://jss.psd401.net:8443 -username imaging -password imaging -allowInvalidCertificate -ssl true
Running system Recon... Overriding JSS Url. Url to be used -> https://jss.psd401.net:8443 Overriding AllowInvalidCertificate -> True Retrieving Inventory Preferences from https://jss.psd401.net:8443/... There was an unexpected error executing the command 'jamf.Commands.CommandRecon'! System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IO Exception: Received an unexpected EOF or 0 bytes from the transport stream. at System.Net.FixedSizeReader.ReadPacket(Byte buffer, Int32 offset, Int32 count) at System.Net.Security.SslState.StartReadFrame(Byte buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte buffer, AsyncProtocolRequest asyncRe quest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at jamf.JAMFCoreComm.JssRequest.AddDataToRequest(WebRequest request) at jamf.JAMFCoreComm.JssRequest.SubmitAsync() at jamf.JAMFCoreComm.ReconPreferences.GatherReconPreferences() at jamf.Commands.CommandRecon.GatherPreferences() at jamf.Commands.CommandRecon.Execute() at jamf.Program.Main(String args)
I've tried using the newest version of Recon.exe with the same result.
Note: My JSS is not behind a load balancer. I've had successful Windows inventory since early June.
Has anybody seen this error?
Solved! Go to Solution.