MDT on standalone server

I have Microsoft Deployment Toolkit (MDT) 2013 installed on a Server 2012 R2 non-domain workgroup only stand-alone server. This actually does work nicely for deploying new servers mainly because the servername is resolved by DNS even though it's not on a domain.
I installed WDM, ADK81 and MDT on this machine using my local admin account.

One thing I noticed is that none of the other local admins on this machine can see any of the deployment shares listed in the Deployment Workbench app. It doesn't give the other users an error when running the app either. All of the admins are in the same local admins group that my account is in - "Administrators".

What do I need to do to allow the other local admins to see the deployment shares listed when they run Deployment Workbench?
jimlock720Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
Where did you place these shares?  If not under your user account i.e. c:\users\username\documents then all they have to do is ADD themopen deployment share
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jimlock720Author Commented:
Oh duh!!! I overlooked the obvious. I am new to MDT - that's my excuse and I'm sticking to it!  Seriously though, the one shared folder that exists is on one of the local system drives. It works of course after clicking open deployment share then clicking browse and  navigating to the actual shared folder. This has always been my problem with being an engineer - I sometimes overlook the obvious. Thanks for the answer and for not making me look like an idiot lolol
0
jimlock720Author Commented:
One more comment - prior to asking here, I searched the 'net and found all sorts of WRONG and misleading answers to this question.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.