It is possible. I've written tools to do this....but creating the tools is the "easy" part. The hard part (at least for a computer or macro to do) is deciding which part wins [in cases where they have a different time stamp].
You typically cannot say the newest wins, because the new file may not be backward compatible....and vice versa about saying the oldest wins. Either way you're likely to at best break mates. At worst, completely lose the design intent. A macro won't check this though, it is going to go through 200 mph ripping this all out. You may not fully realize the damage for years down the line when someone opens an assembly and has no idea what happened.
It takes a human/intern. (I've heard that interns actually are humans, more research needs done here.)
Workgroup? Really? Obviously it does not permit duplicate file names. That's your iceberg. PDM Standard will accept duplicate file names, and with it you can get information out of the database to help you find the duplicates. (Pro even has tools to help you fix the duplicates.)
I'm with Jeff, if you plan on ever upgrading to 2016 or beyond don't go to workgroup. Migrating from Windows to (E)PDM is much easier and you'll have access to standard with any license that could access WPDM.
Trust me when I say Im dealing with a "know all" that has say over mine. My head is bloodied, so is the desk. Im near on giving up.....WPDM was always a POS to start with too.....