Hi, Where do I set the share perms? I've just done the NTFS perms under the drives properties and the Sharing tab. Cheers, Barry.
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Thursday, January 20, 2011 11:46 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Newbe Server 2008 R2
Hi,
Share perms are not the same as NTFS perms, make sure you set both accordingly.
Andrew.
________________________________________ From: blind-sysadmins-bounces@lists.hodgsonfamily.org [blind-sysadmins- bounces@lists.hodgsonfamily.org] on behalf of Barry Toner [barry@barry- toner.co.uk] Sent: 20 January 2011 10:04 To: 'Blind sysadmins list' Subject: Re: [Blind-sysadmins] Newbe Server 2008 R2
Hi Andrew,
I wasn't logging onto the Domain lol. When i rebooted after connecting the laptop to the Domain the log-on changed to the ctrl, alt, del. When i clicked on Other User I was expecting to see a Domain edit box with the UN/PASS like in the XP days. You actually type your Domain now. Domain\UserName Password Password
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Wednesday, January 19, 2011 11:28 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Newbe Server 2008 R2
Hi,
I would forget about seeing the computer in the network browser/network neighbourhood. Can you get to shares on the domain controller by going to the computer name? There are always some default shares on the domain controllers such as sysvol and netlogon, so you can browse to that by using \\dcname\sysvol etc.
One thing to look out for is that you are actually logged into a domain account and not a local account.
By default there are no roaming profiles set up on the domain which is what I believe you meant by your second question, those are set up on a per user basis by redirecting the profile folder to a share.
Thanks. Andrew.
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: 19 January 2011 20:40 To: 'Blind sysadmins list' Subject: Re: [Blind-sysadmins] Newbe Server 2008 R2
Hi,
It looks like I've now joined my laptop to the DC. Thanks for this Andrew. More questions... When looking under Networks I am still seeing the computer in the house that was setup as a Windos Workgroup. I am not seeing as I thought I might the DC with the shared drive I configured.
I can confirm when i go into the Systems properties and Computer Name that I am connected to tx.r2.com and not BTXP the name for the Windows Workgroup.
One final question as I don't 'want to spam you all.. My account information ont he laptop isn't being stored on the DC AD is it? I want to keep this information local.
Cheers, Barry
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Sunday, January 09, 2011 7:33 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Newbe Server 2008 R2
Hi,
Yes, you can do all this with the server. I haven't done much with VPN technology (which you would need in order to get at your files remotely through mapped drives, but it is doable.
When I did this to start with I had a very low spec machine and kept rebuilding it again and again until I was satisfied with what I was learning. I had a hard drive caddy with a couple of disks, so I could take the whole thing down for testing if required. This was of course before virtual machines really kicked off.
Start simple at first and build off, get your AD set up and a laptop or test machine connected to it first before starting to run ahead of yourself.
Hope this helps. Andrew.
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: 09 January 2011 15:38 To: 'Blind sysadmins list' Subject: Re: [Blind-sysadmins] Newbe Server 2008 R2
Hi Andrew,
What I was looking to do was.
1. Use the Server as a File Print Server. I had this in Windows 7 but I'd like to use Domain instead of Workgroup networking. So have the client machines in the house connect to the tx.r2.com Domain I created onthe server instead of using the BTXP Workgroup I did in the past and used Network File/Folder sharing. The printing is working, because I fudged the printer drivers installer.
2. Using my laptop admin the Server remotely.
3. Access files on the hard drives attached to the Server through Networked mapped drives, even when i'm not at home and connected to the internal WIFI.
4. See the client machines at home in AD and for testing apply Applocker auditing rules.
Is this all possible? And if so, how do i do it? I have no real experience with Servers and have only dealt with client machines and Client Desktop Support. I'm completely lost and that 2K8R2 is just sat upstairs at the moment.
Cheers, Barry.
-----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind- sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Wednesday, January 05, 2011 11:00 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Newbe Server 2008 R2
Hi,
You didn't need to create a computer object for the laptop.
If you want to do remote management of the AD from the laptop
the
laptop needs to be a domain member - i.e, so that you can log in from the laptop to a user account on the AD).
The first thing you need to do here is to set the TCP/IP
up
correctly on the laptop or a DHCP server so that the laptop DNS settings point to the box running the AD. This is so that the laptop can see the relevant records in order to connect to the AD server.
Once this is done, test it by using nslookup, for example:
nslookup tx.r2.com (assuming this is the FQDN of the AD you created).
It should give you the IP address of the DC you created. This will have a server name of server.tx.r2.com.
You need then to join the laptop to the domain through the computer properties. When you join the domain, enter in tx.r2.com as the domain name to join, you need to enter a username and password - this account needs to be a member of the domain admins group by default, or has explicit permissions in AD to join machines to the domain. Once the machine joins the domain, you should see the computer object in the computers OU.
Once the machine reboots, log in as a user with domain
Got it logging in now and it created a new profile. I'm seeing the server under Networks and the shared drive, but the perms aren't in effect even though I went into Sharing and added the laptops Computer Name to the permissions and it was able to Discover the laptop using AD. Cheers, Barry. then properties priviledges
in the laptop, it will build you a new profile. You can then install the remote admin toolset and use ADUC to manage the AD remotely.
Hope this helps. Andrew.
________________________________________ From: blind-sysadmins-bounces@lists.hodgsonfamily.org [blind-sysadmins- bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner [barry@barry- toner.co.uk] Sent: 05 January 2011 09:58 To: 'Blind sysadmins list' Subject: [Blind-sysadmins] Newbe Server 2008 R2
Hi folks,
Let me say first of all I've little to no experience of this. Other than a year 3 years back assisting in a large Software House with Server 2003.
I've install Server 2008 R2 at home. I've assigned it as a DC and install Active Directory. I'm flying by the seat of my pants and don't know what i'm doing. I want to be able to log-on to the Active Directory service using my laptop. Poked around in Active Directory and I created a Computer object under tx.r2.com (which is the address I gave my DC). I then created a User Object for myself. Now what? Is there tutorials or something? I can of course sift through the Microsoft documentation, but this is such an massive product and already I am drowning.
Help!
Cheers, Barry.
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins