Community
You don't need to have an active license. Somebody may have downloaded a DWG file from the internet which had the EDU flag. That could include a client or vendor providing files for your use. Now that you've been using it, it's been spreading through your own files. In addition to using a new release to "purge" the EDU stamp I *highly* recommend you do a forensic audit on your files (including blocks, XREFs, templates... everything!) to find the real culprit otherwise it will keep coming back.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
You don't need to have an active license. Somebody may have downloaded a DWG file from the internet which had the EDU flag. That could include a client or vendor providing files for your use. Now that you've been using it, it's been spreading through your own files. In addition to using a new release to "purge" the EDU stamp I *highly* recommend you do a forensic audit on your files (including blocks, XREFs, templates... everything!) to find the real culprit otherwise it will keep coming back.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
Accepted solution
You work your way from known EDU flagged drawings back into your system. What was used in those drawings (blocks? XREFs? Drawings inserted wholesale?) - those should be checked. If those were modified between receiving and releasing the flagged drawings, then they need to be checked. Anything which was used to modify *those* drawings are then checked using the same process. This also includes checking with users who worked on the drawings - are they using DWGs from places other than your central storage? Those need to be checked as well. It sounds like this will track back to whoever sent the drawings, so they should be notified and any further drawings from them screened before you do *anything* with them until they consistently deliver unflagged drawings. If they refuse to fix or recognize the problem it could be time to take further action.
The process is grinding and brutal and time consuming, but you *don't* want this coming back and that will happen if miss even just one instance.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
You work your way from known EDU flagged drawings back into your system. What was used in those drawings (blocks? XREFs? Drawings inserted wholesale?) - those should be checked. If those were modified between receiving and releasing the flagged drawings, then they need to be checked. Anything which was used to modify *those* drawings are then checked using the same process. This also includes checking with users who worked on the drawings - are they using DWGs from places other than your central storage? Those need to be checked as well. It sounds like this will track back to whoever sent the drawings, so they should be notified and any further drawings from them screened before you do *anything* with them until they consistently deliver unflagged drawings. If they refuse to fix or recognize the problem it could be time to take further action.
The process is grinding and brutal and time consuming, but you *don't* want this coming back and that will happen if miss even just one instance.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
