- This topic is empty.
17. January 2012 at 11:25 #7069
I need help with what I suspect has been a commonly asked question – I have searched the forum but I haven’t specifically found the detail that I need.
We have around 30 S10 units at the moment running WTOS 6.x and we have a desire to update these to version 7.x – am I right in saying that doing so will support RDP 7 and therefore Server 2008 R2 Remote Desktop Connection Broker?
I understand that the S10 units cannot accept the firmware due to the larger size of the firmware. I also understand that if this was a more advanced unit then we would just dump the RCA_wnos file into the wnos folder on our FTP server?
As I’m sure you’re expecting, I have done this and I get the compressed image is too big (2685255) error.
Therefore I have seen information that I need to sort out netboot, but I unfortunately haven’t been able to find out exactly what that entails or how I need to do it.
Is this something you wouldn’t mind helping with?
Chris17. January 2012 at 11:37 #21646
I think I’ve missed a step. I believe I need to upgrade to 6.5 first. I will do this first.17. January 2012 at 12:44 #21647
Ok so that has worked.
And it looks as though 6.5 may achieve what I want anyway.
One more query:
On a test client which I have updated successfully now to v 7.1, I notice that it has lost the Terminal name for some reason. I assume it’s because of the netboot process.
Is this avoidable?
We actually configured all of the terminals with a terminal name which contains the name of the printer they should connect to when logging in so we need to keep the configured names if possible.17. January 2012 at 16:46 #21651
Ok, another query.
I have decided that WTOS 6.5 is suitable, but unfortunately I have two terminals which have updated to WTOS 7.x.
So the FTP/WNOS folder has the boot and wnos files for 6.5, but now the two terminals boot into a MiniRom saying NetBoot failed.
Is there a solution to get these two clients running 6.5? Or at the very least, point specifically these two clients to another folder containing the right boot files?
Everything is configured via DHCP so I have a feeling we might be stuck 😐18. January 2012 at 7:48 #21652aLiEParticipant
- Total Post: 320
- Jacked into The Matrix
Once you upgrade a S10 to firmware 7.x a downgrade is (as far as i know) not possible.18. January 2012 at 10:52 #21654
Once you upgrade a S10 to firmware 7.x a downgrade is (as far as i know) not possible.
Thank you for your reply.
What I have done is logged the MiniRom into the FTP as a different user whose home folder contains the v7.1 wnos and boot files.
Seems to be happy with that.
A bit annoying how I have 2 out of 30 on a different version, but that’s my own fault for not testing 6.5 properly before upgrading to 7.1.
Thank you for your help.
- You must be logged in to reply to this topic.