 Rank: Guest Joined: 10/15/2018(UTC) Posts: 1  Location: Toronto
|
Greetings,
Quick question for you guys, is Windows XP still supported? I got some hardware that runs WINXP and I want to be able to remote in. I noticed on the main page it says "Yes" but I get a different story in the supported OS documentation.
Can this still be done?
Lemme know.
|
|
|
|
|
|
 Rank: Administration Medals:  Joined: 5/30/2012(UTC)
Posts: 501
Location: Raleigh, NC
Thanks: 56 times
Was thanked: 82 time(s) in 68 post(s)
|
Good Morning,
We don't post End of Life O/S on our supported O/S page, but .NET 2.0 and SP3 were the only things needed to connect to Win XP, in the past. I didn't have a machine to test, but I would start there. I can't think of any major architecture changes that would affect that.
Mike B |
ScreenConnect Team |
|
|
|
|
|
 Rank: Advanced Member Medals:   Joined: 3/9/2015(UTC) Posts: 80  Location: Texas Thanks: 15 times
Was thanked: 20 time(s) in 6 post(s)
|
I still have a lone XP machine out there, and am able to still connect to it.
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 2/6/2014(UTC) Posts: 316  Thanks: 6 times
Was thanked: 33 time(s) in 29 post(s)
|
Originally Posted by: Jesseb  I still have a lone XP machine out there, and am able to still connect to it. Me, too.
|
|
|
|
|
|
Rank: Guest Joined: 10/23/2018(UTC)
Posts: 1
Location: Chicago
|
We have couple hundred XP systems all over the world
with ScreenConnect installed and working without issue.
All SP3 XP systems w. NET 2.0
|
|
|
|
|
|
Rank: Guest Joined: 11/8/2018(UTC) Posts: 7 Location: WA Thanks: 4 times
|
Have one server 2003 left, and it isn't playing nice with 6.9 at this moment.....
|
|
|
|
|
|
Rank: Administration Medals:  Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
@joshgay1 what specific behavior are you seeing on that one server? Can you post a screenshot? Is there anything within the Application Log in the Event Viewer? |
ScreenConnect Team |
 1 user thanked Scott for this useful post.
|
|
|
|
Rank: Guest Joined: 11/8/2018(UTC) Posts: 7 Location: WA Thanks: 4 times
|
Faulting application ScreenConnect.Windows.Client.exe version 6.9.20755.6879, faulting module kernel32.dll, version 5.2.3790.5295, fault address 0x0000bf93. Server 2003 SP2 If you want a report or access for a bit it can be arranged. @scott Edited by user Wednesday, November 14, 2018 6:44:27 PM(UTC)
| Reason: tag scott
|
|
|
|
|
|
Rank: Guest Joined: 11/8/2018(UTC) Posts: 7 Location: WA Thanks: 4 times
|
Originally Posted by: Scott @joshgay1 what specific behavior are you seeing on that one server? Can you post a screenshot? Is there anything within the Application Log in the Event Viewer? See above reply, it crashes itself so shows connected but isn't...
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Thanks for that, we were seeing similar behavior with the one 2K3 VM we have internally. After some research I couldn't verify that it wasn't a problem with the VM itself but your report makes it clearer that's probably not the case.
I've requeued the defect to be investigating and hopefully the fix isn't too complicated. |
ScreenConnect Team |
1 user thanked Scott for this useful post.
|
|
|
|
Rank: Guest Joined: 11/8/2018(UTC) Posts: 7 Location: WA Thanks: 4 times
|
I see newer 6.9 releases in the output stream but nothing available to download? (and then I go back as it had been 10 minutes, and I refresh the page and there is a beta again).... Edited by user Wednesday, November 21, 2018 12:27:00 AM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
@joshgay1 it should be listed here now. |
ScreenConnect Team |
|
|
|
|
|
Rank: Guest Joined: 11/8/2018(UTC) Posts: 7 Location: WA Thanks: 4 times
|
Originally Posted by: Scott @joshgay1 it should be listed here now. Yes, I managed to catch it likely while it was being refreshed as the download site then added a version, and the output stream may have updated as well, that said I assume 2003 is still a dead soldier for now?
|
|
|
|
|
|
 Rank: Newbie Joined: 10/13/2015(UTC) Posts: 6 
|
Unfortunately we have 1 Server 2003 at our clients. We are having the same issue: Quote:Vastgelopen toepassing: ScreenConnect.WindowsClient.exe, versie: 6.9.21027.6898, vastgelopen module: kernel32.dll, versie: 5.2.3790.5295, vastgelopen op: 0x0000bf93.
We are running: "6.9.21027.6898"
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/29/2015(UTC) Posts: 100 Location: Metro DC Thanks: 27 times
Was thanked: 10 time(s) in 8 post(s)
|
Same thing here with a Windows 2003 client and 6.9.21027.6898.
Mark
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
To follow up we have 3 issues affecting Guests running Windows XP in different ways. One fix did make it into 6.9 but while the second issue has been fixed it was not merged into our master until ~1 week ago thus will not be included until 7.0.
The third issue is still under investigation but it is significantly less impactful to the application and doesn't cause an application crash, to my knowledge. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/29/2015(UTC) Posts: 100 Location: Metro DC Thanks: 27 times
Was thanked: 10 time(s) in 8 post(s)
|
I can confirm that the latest update (6.9.21415.6941) is working correctly with the Windows 2003 client that I mentioned in my previous post (above).
Mark
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
