Jump to content

doup93

Member
 View Profile  See their activity

  • Posts

    18

  • Joined

  • Last visited

Awards

This user doesn't have any awards

doup93's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. doup93
    Word of caution if your server has a hardware RAID controller. You may run into issues running "regular" desktop SATA drives in a RAID configuration: Drives can drop randomly out of the array. Best bet to prevent this is to use NAS drives.
  2. doup93
    It may not work as the board requires ECC unbuffered RAM whereas the memory you linked is fully buffered. As for the number of VM's for that server, it depends on what is being run in these VM.
  3. doup93
    I'd say look into the permissions of each share as well as the security of the folder to which each share points to. I wouldn't be surprised if the only permission defined is 'Everyone'
  4. doup93
    LBFO (Load Balacing Fail Over) is available in server 2012 and can be used with VM's to ensure that. What it does not do is link aggregation so configuring a 4-port LBFO to be used by a virtual switch will not give each VM access up to 4 gb. It will spread the load of all VM's onto that group and if a link fails, it will fail over any VM using that link to another link. http://www.itprocentral.com/overview-of-nic-teaming-lbfo-in-windows-server-2012/
  5. doup93
    Which is the usual best approach but in this case, there are security concerns to be taken into account. Look into how the shares are configured.
  6. doup93
    Correct, Exchange works with AD so users need to be created in AD for Exchange to work. So basically whoever set up the server and PC's created the user in AD then created the users locally but did not join the PC's to the domain. Changing the username on one PC most probably caused the failed Exchange login since that user does not exist in AD.
  7. doup93
    From what you said, it seems the user accounts already exist in AD since they're using Exchange for emails. So the thing missing here is backing up all user information, join each workstation to the domain, login with the appropriate user then move the files back under the newly created profile and configure email. May be missing other things but that's what I see so far.
  8. doup93
    AD can't manage a workgroup. Right now, you need to manually create users on each computer if they want to share files or have no security at all (aka sharing user names/passwords or no security at all on shares). AD will allow you to centralize security, and like Electronics Wizardy said, use a lot of goodies that come with a domain. Best thing is to set up your server as domain controller and make it your DNS server. YOu could also set up DHCP on that server. Then, join all computers to the domain, set up user accounts ,etc. https://msdn.microsoft.com/en-us/library/gg490793(v=ws.11).aspxInsert other media Since it's an accounting office, waiting until after tax season is a good idea.
  9. doup93
    If you are planning to move and want some kind of rack, Startech makes some racks that you assemble yourself. I bought their Startech 42U 4 post rack and it is very sturdy and easy to assemble (didn't have a need to disassemble yet so can't really comment on that except that it would be feasible). Just look for flat pack racks on their website.
  10. doup93
    I had 4 Seagate 2TB desktop drives connected to a RAID controller a few years back and that array worked fine for about 18 months before starting to see 2 drives drop out every now and then. Replaced the whole array with Enterprise drives and never had that issue again. Like leadeater said, desktop drives miss TLER and are not made to be run in a RAID array. I'm pretty sure that upgrading the firmware won't solve your issue. If you do need to run a RAID, get some drives made for NAS or enterprise grade drives.
  11. doup93
    If your router is configured to let port 3389 traffic through and is configured to forward that traffic to your PC then you should use your external IP adress as host name. As for the user name to use, it should be COMPUTERNAME\USERNAME where COMPUTERNAME is the name of the PC as found in System window of the Control Panel. USERNAME should be the name of the user account you want to use. Just make sure that user is allowed to connect through Remote Desktop in the System Properties window.
  12. doup93
    Just going through the list of possible issues: - Your router is configured to let port 3389 traffic through? - What do you enter as host name in RDP? Since you are external, it should be your external IP and your router should be forwarding 3389 traffic to your PC
  13. doup93
    Since it's not domain joined, you should enter machinename\username
  14. doup93
    You'll need a converter too: Converting from vmdk to vhd
  15. doup93
    Actually, you can set up your VM to start before the host OS and even if you don't, it still works: Demystifying virtualized domain controllers
×