57chevvy

Hi, This is unusual as this has been a pretty good Ranger release by my current experience and we have a couple of hundred good installs of Ranger using Windows 7 so far. Would you please confirm a couple of things. 1. The logged in user is in the configured group (Ranger client icon in taskbar) and this is the group Ranger is delivering the configured environment for. 2. The environment/group/start menu/Programs folder (classic mode only) is not ticked as you are using Windows 7 and this is for Vista as there is no classic mode in Windows 7 - Programs placed in folder from start menu in Windows 7 - looks the same. User folder permissions are usually only changed from your preferred settings because the "inherit permissions from parent folder" is not selected and the "grant user exclusive rights" option is in force. Hope this helps. If you need more please feel free to contact. Rgds

Sounds like the clients have a firewall on. Ranger remote requires the following to be open through a workstation firewall Technical Document Number - 441 use the nss option which is the same as Ranger Remote Rgds

If you wan to run Windows 7 with Ranger you will need to upgrade anyway so have a look around is always a good idea. I would suspect that your Ranger hasn't let the shcool down for a good while hence using 5.8 still - value in that reliability for sure. All systems will have their pro's and cons even vanilla MS. Many here like to carve their own route and there is nothing wrong with that. The problem most school have is a lack of correctly skilled resource to manage and develop a network which is where products like Ranger came from by aggregating and simplifying tasks for those without time - nothing has changed. Ranger development has been quiet for a while but it still works well and with a mix of windows 7 and xp clients on the same network which is a plus. The new version promised this summer apparently promises much so worth a look before you trash it. These systems all do much the same thing it is how intuitive the system is to you and comfortable you feel with the product roadmap. We looked at Impero but as a small company still (companies house webcheck) we thought they may have a way to go to support their product development and become a mainstream supplier maybe next incarnation of the network will be their time. Good luck

As con2prt is 32bit software and it will need to be run locally from the workstation if using a Windows 2008R2 server as we found on Win2kR2 con2prt will give unreliable connections when run from 64 bit server. e.g. IF %Location% == Room1 c:\localfolder\CON2PRT /C \\server\printername IF %Location% == Room1 c:\localfolder\CON2PRT /CD \\server\printername

Hi With XP clients either using a roaming profile to an alternate location on the server or a mandatory profile would resolve this. Windows 7 is another issue! Regards.

Hi, If you use a Ranger react task in LANRanger you can get it to block an applicaiotn in a "room" automatically for a period and then relase at a certain time. Rgds

Hi You can check if Ranger is shutting down the .ppsx file by looking at the status log in LAN Ranger. If it is then the username and "violation" will be shown here. It is possibly a title check if it is but certainly the clue will be here if Ranger is causing this. If it is a violation LANRanger will give you the offending string and you can change the setting in the security section of Ranger Administrator to stop this happening for the affected group(s). Rgds

Hi The registry key is HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\TabbedBrowsing The value and name is REG_DWORD WarnOnClose Value 1 (for no warning) If you want Ranger to set this value for you you will need to edit the preshellNT, 9x or Vista .rrg files in the Ranger directory and add the following exported registry branch. The setting should then be changed upon next login [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\TabbedBrowsing] "WarnOnClose"=dword:00000001 Rgds This should work but I cannot accept any resposibility if it doesn't. The preshell files in Ranger are handy for this purpose as they let you do registry merges essentially before Ranger loads and would ban such activity.

Hi It sounds like your account management method (Ranger Account Manager possibly) is set to create the use rprofiles in the users home directory. This can easily be changed using Ranger or whatever you use. The default setting in Ranger creates it there for sure but only because when installed it would not know about an alternative and does not create unnecessary shares by default. So why don't you redirect their roaming progfile to an alternative location on the server e.g. \\server\userprofiles$\username then it would not show up in their home folder location which is possibly what is causing you this irritation. If you need more detail on this please revert. Rgds

Hi Have none of you had difficulty with the copyprofile function as this is the only thing outstanding for me in Windows 7 preparation that is causing real hassle.? Sysprep always fails when this is included. I have read many and various forums on this and it would appear to be not an uncommon problem but as nobody here mentioned this I would be pleased to know more if possible. Basically, we are looking for a way of configuring a "default user" profile to use probably ultimately as a mandatory .v2 roaming from the server but cannot reliably create one locally for this purpose. This was a doddle for XP but Windows 7 appears not particularly enterprise friendly at the moment to me. The Microsoft prose is to only have one account (say administrator) configure that as required with the required personalised settings etc. Make sure no other profiles exist on the workstation and as part of sysprep this will be copied to "default user" during sysprep and then all subsequent logons (to the workstation) will be given this personalised profile. The base Microsft article How to customize default user profiles in Windows 7 and in Windows Server 2008 R2 on the subject is eloquent but does not work. The Brian Lee Jackson one is also helpful but incomplete. It is implied the "other" changes occur to the default profile during the sysprep process although no documentation is available to expand on this. Having used sysprep for several years I am certainly familiar with its operation and am frankly surprised and disappointed by the copyprofile difficulty being encountered. So if you folks have a magic bullet for this I would be pleased to learn more if possible. Rgds

Hi Yes maybe so. I guess we have expressed our views for the consideration of others which is the point of the forum after all. Rgds

Hi Sorry to stir your emotions so much I wasn't trying to start a contest about the value of Ranger just trying to put things in perspective based on experience. If you are having conflicts with user apps, AD and Ranger these are usually just a configuration matter and easily remedied. Ranger do offer a free to use forum for users to express themselves though and considering the amount of registered users on the Ranger forum (5000 registered accounts) and judging by their forum stats there are relatively few issues raised both here and on their forum that appear to remain unresolved for too long. Securus and LanSchool are compliementary products aimed at different markets to Ranger for Networks the Ranger offerings here are Ranger Guardian and Ranger Remote control and should not be confused with Ranger for Networks surely. I do however admit to being a supporter of Ranger for my sins as my experience overall has been positive. Rgds

Hi I don't think it's actually a Ranger problem per se other than Ranger reflects the issue and the Ranger client software needs to give more time potentially to release the last login session as the Microsoft server OS seems to do this "when it is good and ready" (I am not a developer just an implementer). The problem only seems prevalent with Windows 2008 server (Vista technology here we go) and then only occasionally in my experience. I haven't ever found a way to do this within a native Windows environment from NT 3.51 and up. Any posts I have seen on Microsoft forums in relation to this have remained unanswered. It was a doddle on Novell Netware but since Microsoft blew them away its one of the niggles that people would like but hard to achieve. Rgds

Hi If you use a user without Ranger security applied (Ranger Administrator \ Security \ groups {select group) \ settings untick "apply security" does the issue still occur? Also try a higher level user e.g Rangermanager Rgds

Hi This is a current issue only with Ranger 7.0.0.4 but only for some users who use the "restrict user logons" to 1 feature for groups in Ranger. If set to 2 the issue does not occur. I understand that Ranger development are looking at the issue now and a fix will be published shortly. FYI the BETA Ranger 7.0.0.5 happily does not appear to display the issue. Rgds

Hi I would do the following: 1. Check policy settings under environment in Ranger Administrator for Rangermanagers group. 2. If just this user (domain admin equivalent) delete profile (roaming &/or local) 3. Check shortcuts offered point to correct place -maybe recopy from local machine best idea 4. As Rangermanger you should also be able to see local drive C:\documents and settings\all users so try shortcuts there too. Rgds