Jump to content

d-taylor

Members
  • Posts

    88
  • Joined

  • Last visited

Reputation

62 Excellent

1 Follower

About d-taylor

Personal Information

  • Occupation
    ICT Network Technician
  • Location
    Norton, N. Yorks
  1. So are you saying that I should add my domain name to this list, or it will query the domain automatically as a domain member? The issue I am having is this: Weird DNS issues, DC's not seeing the domain - Spiceworks
  2. Hi, I'm having some odd DNS issues I'm struggling to get to the bottom of, which I started investigating months ago. I'm looking at the DNS suffixes on the DNS server when you view the network adaptor properties, click on the advanced button in the IPV4 properties, then click the DNS tab. Could someone with at least 2 DNS servers on their network please look at the attached screenshot and tell me if the settings match their network or not? Also, I need to know if you use .local in your domain name or not (e.g: schoolname.net, schoolname.org, schoolname.local etc.) as we don't, and I'm wondering if this has an impact on this setting or not. We're also an RM CC4 school, so would be interesting to see the same info from another 2 or more DNS server RM School. Many thanks, Dan
  3. Hi, I'm looking for recommendations on AV installation companies in the North of England. We want to make sure we are getting best value for money and we think there may be better suppliers out there. We have some Activboard mk 2's with short-throw projectors, and we are getting these retro-fitted with Casio short throw LED projectors with adaptor brackets. Whilst we will attempt long throw projectors in house, I still want to go out to an AV company that will supply and fit for the short throw installations. Does anyone have any recommendations? Thanks, Dan
  4. Just implemented this ADM template, nice quick fix! Thanks!
  5. You just need to restart the RM Service Host service on student machines, no need to delete any files. If you need to restart RM Service Host on a large number of workstations regularly, I'd recommend logging a call with RM
  6. Cheers Jason, that's more concrete then I can think of at the the moment, I'll pass that on Dan
  7. And they love shifting their employees between departments and job roles every few months. Just to keep us on our toes when we ring up
  8. I hope so! Emailed them last week, still waiting for a reply.
  9. Many thanks, I would only consider clean install, but I can't come up with a convincing enough argument on WHY I'm right- I just know I am. Jay, do you have any more detail on what went wrong so I can show some examples? Thanks, Dan
  10. Good afternoon! The College has decided to move away from CC4 to a vanilla network for reasons I won't go into here. What we haven’t decided on yet is how to achieve this. There are two methods we have discussed. Method 1 My preferred option is to build a clean network in the background, on virtual servers on it’s own VLAN, and test heavily in the isolated environment, with help and input from the users. When the network is good and ready, during the summer holiday, turn the CC4 network off and move the vanilla network onto the main infrastructure. Based on the CC4- CC4.3 migration that happened here, this would involve 1 week of complete downtime, 1 week of limited data whilst I restore it to the new domain, and from then on computers would need to be rebuilt, so staff would be restricted to where in the school they could work (not a massive issue in the summer holidays.) There is a lot of work involved with this route, but on the whole the clean break from the upgraded CC4 network to the CC4.3 network has paid off massively, in that I am no longer fighting issues each week caused by the upgrade, some of them which were very long and drawn out. I am very keen to avoid fighting unknown issues for the next x amount of years. Method 2 My colleague's preferred method is to create new OU’s in Active Directory, as much of the RM network group policy is contained in the establishments OU. In the new OU’s, our own group policies can be set up and configured, and computer and user objects instead moved to there. The network in theory could be gradually migrated across, moving users/ computers into the OU’s a few at a time. Also, there would be no issues with moving data or NTFS permissions (see below!) as all the groups SID’s will stay the same. When we did the CC4> CC4.3 migration (which used method 1), the first 2 months of term were disruptive, and my colleague seems determined to avoid this at all costs. While I want as little disruption for the College as possible, I would rather see 2 months of teething issues than years of hidden faults that will be a nightmare to resolve. Those 2 months of disruption are nothing compared to the 3 years that followed our initial CC4 install. The two big issues with the migration were self inflicted- we went from about 30 Windows 7 stations to the whole site as Windows 7, yet no-one had tested all of the remaining software for Windows 7 compatibility. I had also put 'check remaining NTFS permissions' on the gant chart I created and assigned the task to someone else, but this wasn't carried out properly, so when the users came back there were quite a few issues accessing shares. We have learnt from this and it wouldn't happen again. I feel the second method of a gradual migration will cause issues further down the line, and lingering RM components still on the network could cause issues and making solving what would normally be a simple Windows network problem more difficult. However, I can’t give technical details of what these issues might be. I have some incline as to what could go wrong, but as I don’t know in as much detail as RM how CC4 works, and I only have 5 years networking experience under my belt. I feel I’m not best placed to answer these questions. There’s also things I could’ve missed out. I would greatly appreciate the community's opinion on what could go wrong using the second method to move away from CC4 -or even if they think it would work well and I'm coming from it the wrong way Some of my inclines as to what could cause issues include: • Settings that could still be in the Default Domain Policy, which is outside the Establishments OU • Changes RM have made to the active directory schema • The CC4 build process interfering with WDS • Does CC4 write anything into the user profiles that would be undesirable to carry forward onto a vanilla network (e.g: custom RM reg settings in the NTUSER.pol files?) • RM software components still running on the servers after we move the computers and users out of the OU’s (e.g: the RM database) • What changes have RM made to the registry on the servers? Given how service host issues have caused issues with basic Windows features in the past (e.g; logons) • What happens if we move users into the new OU’s and they roam between computers still on CC4 (where settings are applied by custom ADM templates that control the RM software) and non-CC4 stations? • How well will we be supported in this configuration? From our meeting with some RM guys, it seems that this has not been attempted before, it has always been a clean migration The above list isn’t meant to be exhaustive, it’s just some thoughts that came to mind. I am really interested to know what you guys think that I've missed out/ am struggling to explain Many thanks, Dan
  11. Could also be set in two places, the All Users registry policy, plus the individual policies (Standard, Staff etc.) Make sure it is changed in both. However, I always do this by deploying the wallpaper to the local hard disk first, either by batch file or MSI, so each user isn't pulling down a 10MB bitmap file each time they log on.
  12. I've not needed to use the Server 2003 ones fo ra while. If you are fully up to date with RM updates, you can take the DNS stop and start out, and see if it runs
  13. Done: http://www.edugeek.net/forums/scripts/107273-scripts-restart-rm-service-host-cc4.html#post918270 This might also be useful: http://www.edugeek.net/forums/network-classroom-management/107272-quick-fixes-common-cc4-problems.html#post918263
  14. As discussed in another thread, run on the FRDC to solve many niggly CC4 problems that come up Server 2003 Server 2008 R2:
  15. A quick reference sheet I have created for my team which I thought CC4 Customers might find useful: Start menu shortcuts not delivering properly Reassign RM Desktop Agent and RM Keeplist. If this fails rebuild Drive mappings and printers not delivering properly Reassign RM Computer Manager Query. If this fails rebuild Builds keeps failing Single computer repeatedly fails: If infrastructure is suspect (e.g: Room2a) try building in a known good area If still failing delete from RMMC and try again If still failing delete from RMMC and do an FDisk and use a build disk If still failing follow the following procedure: • Delete from RMMC • Wait for 5 minutes, then in the forest root server go into DHCP and 192.168.0.0 scope, address leases, and find the station name. Make a note of it’s IP address, then delete the station from DHCP. • Go into DNS, forward lookup zones, domain name, then look for the station (you can browse by hostname or IP) and delete the entry • Still in DNS, go to reverse lookup zones, {subnet IP address was on}, (again you can browse by hostname or IP address) and delete the entry Wait 5 minutes then try the build again Batch of builds repeatedly fails: Restart RM service host on forest root server Strange behavior in RMMC Close and re-open RMMC. If this still persists, restart RM service host on forest root server If this still fails, do a full service host restart How to do a full service host restart 1. Whilst logged in as administrator onto the forest root server --> Start --> Administrative Tools --> DNS --> right-click on --> All Tasks --> Stop 2. Then restart the RM service host as follows: 1) On the forest root server, open Services and Stop RM Service Host. 2) Delete the folder and contents of C:\Program Files\RM\Connect\Comms\HostedProxies\. 3) Delete the folder and contents of C:\Program Files\RM\Connect\Comms\ RemotingHost\. 4) Browse to C:\ Documents and settings\all users\application data\rm\connect\comms\ and rename seccache.rmcache to oldseccache.rmcache. If SR1 is installed the file name will be seccache2.rmcache. 5) Start RM Service Host . 3. Once this is done, back in DNS right-click on All Tasks --> Start --> wait for about 5 mins and check
×
×
  • Create New...