Even possibly worse is that by super-descriptively naming the computers means that anyone with crash log or trojan/mapping software can map out a firm's or an agency's approximate or exact seating and office arrangement. This could be an extreme security hazard, and could in advance open the company to employee-initiated lawsuits against the company.
This could be an issue in that companies may want to cause the US government to pass laws that software vendors MUST NOT collect nor even embed in the software a collection of machine and geographic information. JUST the crash, the generic or specific type of 3rd party java/active-x/C++/etc code running, and the machine os/rev/patch level, the date and time, and a few other non-identifiable bits of info. But, all the sites visited, the location of the hardware, the user login name... hell, who can know what the crash logs collect when many if not most of them convert the stuff to hex or some other non-human readable characters? (Yes, those with skills can reverse engineer most of this, but the lay person may want to know there corresponding, readable bits before allowing the log to be sent.)
This guy's asking the question could serve the purpose of warning him that a naming convention should not give up TOO much information that could be nefariously exploited by unauthorized recipients of such scheme. Internally, the scheme is likely to be fantastic if not overdone, though.
Unfortunately, i'm thinking what i wrote may be pointless because the crash logs are just collating information already in the system's ram or files that any decent programmer can obtain. So... maybe what i wrote is meaningless... a waste of time...