Having Problems With Some Roles Or The Whole Configuration

Synergi

New member
Joined
Jan 5, 2010
Messages
3
Hi guy's/girl's

before I start sr for my bad english x) If you cannot understand anything please ask ^^

What is exactly the problem??? Thats a nice question if I could answer it I would not write to you x) So mainly let me first describe what I'm exactly doing or planing to do ^^

First of all I have only one physical machine its an typical Server with good components. I'm building up the server structure for a school. They are using about 40 Clients with about 4 different types of administration groups like teacher, direktor, student,... The server should host an Routing and Ras server, DHCP & DNS, Domain Controller, Fileserver, Printserver an last but not least Application Server or sth like that (i want to set up the applications once and installing it on all the clients.) The Server software is an Windows Server 2008 Enterprice R2 x64. The Clients are all Windows 7 x86. So now im going to describe you the problems:

First the way i did it many times ^^

First install Windows Server 2008 Enterprise R2 via USB Stick Clean only 1 Partition formated with windows Installer. (1TB)
Next im setting up the main abbilities like server name, Remote Acces allowed, activation, update rules and on and on.
Then doing the update finding about 12 updates (04.01.2010)

Okay now i go on installing the different roles

Domain ...
Setting up the Domain Controller via dcpromo.exe
during this installing DNS via dcpromo.exe.

BTW the server has 2 Network Cards one into local Area network and the other one into Internet. Both IP-Adresses are not dynamically they are set fixed. On the local area network im using 192.168.0.1 with subnet 255.255.255.0

First Problem when im setting up the domain controller while Server is connected to the internet it takes about 10 hours. When disconnected it goes really fast. I made an new complete structure (sr dont know how it is named in englisch "Neue GESAMTSTRUKTUR und Neue DOMAIN"

When Im trying to reboot after it finished nothing happens.

Next problem. During of many isntall tries the Domain Controller works.

Now i went on with installing the DHCP and then the Routing & Ras. If only 1-2 Client are active everythign worked fine. But suddenly i got IP Crashes for all the other Clients.

Next Problem -> I DONT KNOW HOW TO SET UP AN APPLICATION SERVER ^^ I want to host for all Clients Office 2007 and other Stuff. Maybe you can give me a hint where i can read something about this topic.

Next Problem -> I'M NOT REALLY FAMILIAR with setting up the POLICY for the compelte DOMAIN maybe also a hint ^^ THX


Maybe anyone of you have time to help a little bit. I'm really newbie in the topic Windows Server. In know what i want to do and what is possible but how !!! x(

THX to all

mfg Synergi
 
I'm going to ask you some questions and give you some places to look for other things.

First Problem when im setting up the domain controller while Server is connected to the internet it takes about 10 hours. When disconnected it goes really fast. I made an new complete structure (sr dont know how it is named in englisch "Neue GESAMTSTRUKTUR und Neue DOMAIN"

When Im trying to reboot after it finished nothing happens.

What do you mean by "nothing happens?" It doesn't boot? It doesn't power on? Nothing changes?


Next problem. During of many isntall tries the Domain Controller works.

Now i went on with installing the DHCP and then the Routing & Ras. If only 1-2 Client are active everythign worked fine. But suddenly i got IP Crashes for all the other Clients.

I don't know what you mean by "IP Crashes." Do they not get an IP address from DHCP? Do they get an address but then they don't work? Something else?


Next Problem -> I DONT KNOW HOW TO SET UP AN APPLICATION SERVER ^^ I want to host for all Clients Office 2007 and other Stuff. Maybe you can give me a hint where i can read something about this topic.

It sounds like you want to set up Terminal Services. This is also called Remote Desktop Services in Windows Server 2008. This means that the clients use Remote Desktop to connect to the server. This page has information about RDS and how to set it up in Win2008.

Next Problem -> I'M NOT REALLY FAMILIAR with setting up the POLICY for the compelte DOMAIN maybe also a hint ^^ THX

Group policy can be complicated and it will take some study to be comfortable with it. In a school environment, when you will have students logging in to the domain controller as a terminal server, you will really want to make sure that you lock things down. Like messing with the registry, you can really cause problems by misconfiguring your policies. If you aren't familiar with group policies, there are a lot of webcasts here with explanations. Here is a decent set of policy info for terminal services under Windows 2003 most of which will still apply with 2008. The National Security Agency actually has some decent guides for group policy and security, but unfortunately they haven't published any Win2008 guidance, yet. You can google a lot of group policy info.
 
Hi Matt,

@ What do you mean by "nothing happens?" It doesn't boot? It doesn't power on? Nothing changes?

-> The Windwos Boot Logo appears and then Black Screen no Login Screen. I let it work about 10 hours nothing changed just a black screen.

@ I don't know what you mean by "IP Crashes." Do they not get an IP address from DHCP? Do they get an address but then they don't work? Something else?

-> The DHCP Server Realeases an IP to a Client but didn't save the Release so the Server forgot that the IP is reserved for an Client. Antother Client want an IP and the Server releases for the Client the same IP as before because he didn't saves the Release and on and on ==> All Clients have the same IP and the Network Chrashes (sr I'm from Austria and we often use English words but it often is nor real English like "IP CRASH" x))

@ It sounds like you want to set up Terminal Services. This is also called Remote Desktop Services in Windows Server 2008. This means that the clients use Remote Desktop to connect to the server. This page has information about RDS and how to set it up in Win2008.

-> I'm not sure if my Answer is correct but if this is it what i know about Terminals that there way is to host sth like an Application. But what i want is to install on Clients with some Clicks an Setting with Applications. An example:
I Set up on the Server Office 2007, Visual Studio 2008, Dreamweaver and on and on. NExt i want to do sth so that this software is installed on all Clients I dont want to host them ^^ or if host is the better way maybe change my mind x)

@ Group Policies

-> THX for help ^^ x)

mfg Synergi
 
@ It sounds like you want to set up Terminal Services. This is also called Remote Desktop Services in Windows Server 2008. This means that the clients use Remote Desktop to connect to the server. This page has information about RDS and how to set it up in Win2008.

-> I'm not sure if my Answer is correct but if this is it what i know about Terminals that there way is to host sth like an Application. But what i want is to install on Clients with some Clicks an Setting with Applications. An example:
I Set up on the Server Office 2007, Visual Studio 2008, Dreamweaver and on and on. NExt i want to do sth so that this software is installed on all Clients I dont want to host them ^^ or if host is the better way maybe change my mind x)

Aha, you may want this then: Remotely install software using group policy. That says 2003, but at the bottom it shows that it also applies to Server 2008. You may find that, though, that some settings have moved slightly in server 2008. If you open Group Policy Management Editor from Administrative Tools, you'll find software installation under Policies >> Software Settings in either Computer Configuration or User Configuration depending on whether you want to Assign or Publish it. (See the link for the difference.)
 
@ I don't know what you mean by "IP Crashes." Do they not get an IP address from DHCP? Do they get an address but then they don't work? Something else?

-> The DHCP Server Realeases an IP to a Client but didn't save the Release so the Server forgot that the IP is reserved for an Client. Antother Client want an IP and the Server releases for the Client the same IP as before because he didn't saves the Release and on and on ==> All Clients have the same IP and the Network Chrashes (sr I'm from Austria and we often use English words but it often is nor real English like "IP CRASH" x))

What does your DHCP configuration look like? What is your IP range?
 
I have captured a little bit more detailed Error for the AD-DC Install no Boot Problem:

Okay I install clean Windows Server Enterprise 2008 R2

Update it and set up everything -> WORKS FINE and Fast REboot

Then i install the server Role AD -> PERFECT Fast REBOOT

Now I activate the DC via dcpromo.exe and isntall via this assistant DNS, New Root and Strukture and Domain, and GO (No changes in Save Pathes and Password is set)

It takes about half - 1 Hour until it restarts.

After Restart it takes about 1 Hour until I see Black Screen with Mouse Pointer. This Screen stays about 2 Hours then the Server automatically RESTARTS and everthing starts again.

?????????????????????

VERY STRANGE or isn't it?

@ Matt THX for Help with Applications nice this is it what i wanted.

@ Matt DHCP:

IP Range 192.168.0.100-200
Gateway 192.168.0.1 (Server RAS & ROUTING installed)
DNS 192.168.0.1 (Server DNS with Forwarding)
Router 192.168.0.1 (RAS ROUTING)

mfg Synergi
 
Now I activate the DC via dcpromo.exe and isntall via this assistant DNS, New Root and Strukture and Domain, and GO (No changes in Save Pathes and Password is set)

It takes about half - 1 Hour until it restarts.

After Restart it takes about 1 Hour until I see Black Screen with Mouse Pointer. This Screen stays about 2 Hours then the Server automatically RESTARTS and everthing starts again.

?????????????????????

VERY STRANGE or isn't it?

After further investigation, it appears that a number of people have had this same problem installing 2008 R2. They seem to have gotten around the issue by disabling write caching on the drive where active directory is installed, but for others that didn't work and they don't seem to have found a resolution.

It could also be some kind of DNS problem. Is the server IP info pointed to itself for DNS? Are any of your NICs set to DHCP?
 
Back
Top