Solved

domain to workgroup

Posted on 2014-01-16
3
393 Views
Last Modified: 2014-01-16
Dear Experts,

I am in process of replacing a Windows Server with Active Directory, no Exchange Server.
This server is only acting as a file server, and also holds QuickBooks and Sage Act! shared data.
As I was getting ready to do this, it occurred to me that this server may not have to be a domain server.  ( Only 5 users, 2 shared printers.)
I did a server migration before, and it took a very long time.
Would it make more sense for me to start all over, take all client PC's off the domain, create a workgroup, and just reattach client PC's again?  Are there any problems that may arise if I did that?

I see nothing that needs migration if I did that.   QuickBooks and Act! need to be reinstalled anyway.
Please advise.
0
Comment
Question by:yballan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 10

Accepted Solution

by:
remmett70 earned 250 total points
ID: 39785505
I would say it is less work, and safer adding the new server, migrating AD and moving file and print shares, than dropping everything back to a workgroup and starting over.  You can break the process up into parts, making sure each is working before moving to the next.  
 
If you start from scratch, your users profiles on the PC will need to be redone also.
0
 
LVL 17

Assisted Solution

by:Chris Millard
Chris Millard earned 250 total points
ID: 39785532
One of the main drawbacks of the workgroup environment are the user accounts. Say for example you had a shared folder on the server and 5 PCs. If just you alone needed to have access to the shared folders, then you either have to make the share available to "Everyone" or you need to share it to specific users. You then have to have an account on the server and on each PC with the same username and password just for you to access the shares. It just gets messy to manage. Of course with 5 users, 5 PCs and 1 Server, that could equate to 30 user accounts spread over the workgroup!
0
 

Author Closing Comment

by:yballan
ID: 39785650
Thank you, remmet70 and roybridge, I will stick with domain.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question