I just heard from a coworker that the use of handheld devices while driving will become illegal by January 1, 2010. That’s only a couple of days away. More specifically, he says that the use of hand-held cell phones, Blackberries, other smart phones, and any other electronic devices while behind the wheel will be forbidden and if caught will result in fines. Ouch. We cannot even use text or email while behind the wheel, and forget about portable games like PSP or Nintendo DS or watch DVD movies. I don’t use portable devices anyway but am addicted to using my cell while on the road (stopped and waiting in traffic of course).
This will be a major setback for me and will require some readjustments on my driving habits. Driving is a big part of the services industry so this could mean delays in response. Oh well. it just means we have to plan well in advance and communicate to people of the lack of communication while in transit. It is for the safety of everyone so I’m glad its finally reached British Columbia.
For tips on safe driving from Transport Canada check out the following link: //www.tc.gc.ca/eng/roadsafety/safedrivers-distractions-index-52.htm.
Have a safe Christmas Holiday season.
I had a lot of problems installing Active Directory onto a second Windows 2003 Server Standard. As part of a two step process of decommissioning Active Directory from the main server and only running AD on the second server, I had to first complete DCPROMO on the second server. The DCPROMO partially completes and errors out at the final SYSVOL share creation. The event logs say that it is unable to complete AD installation until SYSVOL is fully replicated. The issues pointed to DNS so I spent a lot of time fixing that. I made sure DNS Server service was not installed on the second server and that all the CNAME records were correct. I then downloaded the Resource kit and ran DCDIAG /TEST:DNS and NETDIAG. The DCDIAG resulted in frsevent errors. I didn’t know how to fix a partially installed AD on the second server so I had to uninstall AD multiple times, taking stabs at different types of fixes. The reinstall unfortunately takes a long time to run so I had to make sure the fixes I applied produces positive results.
After numerous trips to forums and technical blogs, I searched thru the system log shows event ID 13555 on the main source server and found this link //www.eventid.net/display.asp?eventid=13555&eventno=572&source=NtFrs&phase=1. I was focusing on the ntfrs errors on the second server thinking the issue was with the destination server. I didn’t think the issue was with the source main server. This links says that a corrupt ntfrs jet database could prevent successful SYSVOL replication. It made sense that if there was an nfrs jet database corruption, this would break DCPROMO. I followed the fixes documented in the link, which includes stopping bot netlogon and ntfrs services; deleting the contents of \windows\ntfrs\jet folder; then recreating the jet databases after netlogon and ntfrs services are restarted. This fixed the errors on the source main server, which fixed the DCDIAG errors, which eventually allowed me to complete the DCPROMO onto the second server.
After AD was installed onto the second domain controller, removing AD from the main server was easy. Hope this helps you out if you ever find yourself in this predicament.