Jump to content

Recommended Posts

Posted

When I took over a CC3 network last year, I was given a day's briefing from an extremely knowledgeable RM support partner that the school had a contract with.

 

One of the few things he told me never to do was to try and rename a workstation.

Posted
Its a pain, you move a computer from one location to another and you have to rebuild even if it has the same package assignment. grrrrr (am on cc4)
Posted
Because I said so! ;b

 

Did you have some specific question in mind?

 

yes why does RM CC(whatever) require you to rebuild a workstation just to give it a different name?

Posted
Its a pain, you move a computer from one location to another and you have to rebuild even if it has the same package assignment. grrrrr (am on cc4)

 

 

errm no...

 

You can move location with out rebuilding well I certainly can. Granted we do not name our stations with the area in all our stations have format XXX-stn-001, XXX-stn-002 etc personally I do not think you should name a station xxx-heads office, xxx-ict1. In previous years we moved the stations about way too much to make it twice as much work if had to even change the name with our numbering can move them anywhere we want no issue.

 

@oxide54

 

As it uses the station name to reference station in several places within the RM postgres database and it adds a layer of complication in which I can see. I also can see been useful if it had been added as part of CC4 (and probably number one feature that has has been requested many times).

  • Thanks 1
Posted

You can rename CC3 stations. Involves a good search of the registry on both client and server as well as renames of the station ini and possibly the AD. It works and it *seems* reliable BUT the time and hassle makes rebuilding a far easier task. Plus what's the problem with a rebuild - other than time, it'll leave you a lovely and fresh station ;) You could patch the point to a Gb link temporarily for rebuild purposes to help for speed.

 

 

* When I say seems, I also mean this is NOT supported by RM, or even recommendable in a live environment.

Posted

@russdev - sorry late night answer = gobbledy gook.

 

I should of said - we move a computer from one room to another (then do the same with the console), yes it does work if you want to leave it there but to tidy the console up we rebuild the computers to the correct name/number so its easy to refrence later when you go back to fix them.

If only there was a script rather than a 2 hour rebuild (roughly)

Posted

@synaesthesia not recommended at all. 1 slight mistake and goodbye server!

 

RM did say they were going to fix this in CC4, whether they have or not is a different issue. I personally steered clear of RM CCx because I saw how it was in another school, and they were pretty much stuck with it (short of rebuilding all domains etc) which I did not want.

 

Perhaps someone can do write up a script, which allows you to do the registry without messing the server!

Posted
There are no irreversible changes made to the server, that's not so much the worry. Point was a quick rebuild wont do any harm. You can also help by creating smartclient images of the stations saved to the RMR/boot manager backup partition - saves a good hour. Plenty of ways and means.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...