Unable to create a separate deployment share (Deploy$) on a remote server > Deployment Forum Community Forums

Friday, January 09, 2009

Library

Resources

Community

About

Community » Forums

Member Login

StandardLiveID

User Name:

Password:

Remember Login

Forgot Password ?


Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Unanswered Active Topics

Forums Search

Forums > Deployment Solutions > MDT 2008

Subject: Unable to create a separate deployment share (Deploy$) on a remote server

Prev Next

You are not authorized to post a reply.

Author

Messages

Davies

Posts:1

05/14/2008 11:34 AM
I am unable to create a separate deployment share (Deploy$) on a remote server. The error message “The share name already exist on the machine”. I have just upgraded from Deployment 2007 to MDT 2008. My upgrade path: I upgraded to the latest version of WAIK VISTA SP1, I uninstalled Deployment 2007, removed each deployment share, deleted each build type and rebooted the server. I wanted a clean install of MDT2008. I installed MDT 2008, added the components, task sequences, created MDT database and created each (LAB, Network, and Media) build type local to the server. Everything is working as it should. Here is my problem. I try to create a deployment share called Deploy$ on a remote server. I receive an error message that the share name already exist on the machine. If I change the share name to Deploy1$ I am able to create the share. I have local administrator rights on the deployment servers. I have rebooted the both primary and secondary deployment servers and still unable to create the Deploy$ share. I have verified there is no share name (Deploy$) or deploy directory on the server. I must be missing some step. Please give me some suggestions on steps to resolve this issue.

Tim Pomerleau User is Offline

Posts:16

05/30/2008 6:07 PM
Don't know for sure if this is it, but the MDT may be erroring because it is reading your Network deployment point (Which by default is a Deploy$ share), and disregarding that you are putting it on a different server.

You are not authorized to post a reply.

Forums > Deployment Solutions > MDT 2008 > Unable to create a separate deployment share (Deploy$) on a remote server

ActiveForums 3.7

Forum Policies

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.

Privacy Statement | Terms Of Use