Thanks Mike for the clear, sequential steps to configure the service. Would you please point me to the right video in 70-411 that I can watch and thoroughly understand the concept before selecting the right choice for the above question. (given I knew the correct answer through answer key)
Why does the service, e.g. DNS service, need to run as a group Managed Service Account? What happens if it does not? I googled and had a slight idea that running a service as a group Managed Service Account would eliminate the administrative task of password management. What password management does it refer to? I do not understand, given that your response briefly mentioned about password?
A. From the Services console, configure the recovery setting.
B. From the command prompt, run sc.exe and specify the config parameter.
C. From the Window Poweshell, run the Set-Service and specify the -PassThrough parameter.
D. From the command prompt, run sc.exe and specify the sdset parameter.
It appears that I need to clearly grasp the concept in order to rule out wrong choices (by understanding what exactly the statement of each choice mean) before arriving with the final correct answer.
I encountered a question from 70-410 practice exam as follows:
Your network contain an Active Directory domain named contoso.com. The domain contains a server named Server1. The Server1 runs a windows server 2012R2. You create a group Managed Service Account named gservice1. You need to configure a service named Service1 to run as gservice1 account
How should you configure Service1?
I followed exam objectives presented through videos from 70-410 and could not have figured out what exactly the question meant. All I know is that the group Managed Service Account is a default container in AD Users and Computers. How does this account associate with a given service? Is it analogous to a user account placed in the Users container?
Would you please explain the above question along with technical concepts involved within the question context with diagram or simple example that I can follow?
Would you please direct me to appropriate sources or crash courses about Netware (Novell) on which that I can quickly grasp key features?
I am currently trained on MCSA, preparing to take 70-410 exam and starting on 70-411. Given earned knowledge via itpro.tv learning, How can I relate knowledge from 70-410 and 70-411 to this Netware (Novell) in term of command lines, administrative tasks (e.g., installation, configuration, or similar).
Any input or suggestion is appreciated
Thanks Ronnie for the clear explanation, clarifying my point of confusion between ROUTING and NAT.
a.) If so, I can route a private IP address from DC to a public IP address, without NAT configured, as long as one of the network adapter interface of the Edge machine must be set to an ISP-assigned public IP address. Is my understanding correct?
b.) In the Routing Table from the Edge machine, the second entry shown as
0.0.0.0 0.0.0.0 192.168.0.1 means that the edge machine can route to any specific sub-net, without NAT configured, in the private network only. In another word, it is LAN routing not WAN routing. Am I right?
Correct my assumptions above if they are misunderstood.
Again, thank you, Ronnie, for your pertinent feedback that gave an insight into question in discussion.
SECTION: Configure Network services and Access
OBJECTIVE: Routing ONLY
Suppose that the public facing network adapter is assigned to a private IP address, e.g., 192.168.0.1, on the subnet 192.168.0.0/24, instead of 184.108.40.206. Is it possible to ping from DC to an public IP address,.e.g, 220.127.116.11 (which is IP address of the google.com), given that NAT is not configured on this scenario. When I tried this, I could ping from DC to any machine that belong to 192.168.0.0/24 subnet but not any public IP address. What is wrong here? I checked the routing table on EDGE machine, and it showed as follows:
My physical host machine uses 192.168.0.1 as a default gateway to access Internet. From the screenshot above on Persistence Routes, I thought the second entry would route packet from any network, including pubic network, to default gateway which can route the packet to destined public IP address, Would you please clarify the what Persistent Routes exactly is doing here?
Also I am wondering how you can assign a network adapter interface to an public IP address. Given that I have a modem and a router, should I disable NAT feature on both modem and router so that ISP would directly assign one of my network adapter interface of the EDGE machine to an public IP address?
Thank you for your instruction,
Thanks Rick for putting up your constructive thought into this post. Yeah, DHCP option 60 should be enabled because both DHCP and WDS are installed on the same server (for lab environment only). If I understood correctly, the enabled DHCP option 60 means that DHCP listens on port 67 and the WDS on the 4011. Correct me if I am wrong
I am still learning windows server 2012 R2 and struggling to grasp all type of services and naming from Microsoft terminology, given that I have not used with any type of server OS platform, including windows NT. It is like a sixth grader tries to learn materials from twelve grade.
Learning to minimize ignorance but not to aim achievement!
Thank you for your spending time to reply my post. It was close to it, Ronnie. It was about the IP address mistakenly set on the TFTP server. When setting the static IP address on the domain controller server ( on which WDS was installed) virtual machine, I did not check it against the used IP addresses. My physical machine also had the same IP address as that of this domain controller server virtual machine. These two machines (virtual and physical) had the same IP addresses, silly me. Consequently the DHCP kept wondering which IP address was actually assigned to TFTP server before directing PXE boot client to the right TFFP server. Mainly the issue was resolved.
Next time, I try to replicate the same silly scenario (both physical and virtual machine with the same IP address) and ping to itself to see if anything interesting comes up, given that both machines still had the access to the Internet at the time of error occurrence.
For learning purpose, I found the screenshot (see below) for those who learn by visual aid and experiments, including me, and might run into all sorts of problem with WDS. it may serve as a road-map (a starting point) to figure out solution or to rule out false assumption and to pinpoint the true cause of the problem. It is better to understand logic/process by pictorial presentation with clear explanation to each of the components involved and to how one interacts with one another in sequential order. Microsoft notoriously came up with an abundant pool of headache terminology and often give learners much of difficulties and unnecessary challenges. One who is well familiar with Microsoft technical terms either has worked in the related field for years or must have gigabyte-sized memory chip planted in his/her brain to memorize a great amount of Microsoft terminology and its abbreviation.
Of course, it is still valuable to have a backup from MCSE certified professionals as a guide to assisting learners to have a clear mental image of how a particular service work and its related components within Microsoft OS)
I followed the episode presented on the WDS /capture image with SYSPREP and encountered the error below. I read the another post regarding WDS and PXE boot and had no clue to try out on this case. Please advise. Thank you
Below is DHCP configuration screenshot. For lab environment, placement of WDS in the domain controller server is for easy follow-up, given that it is not a good practice (for security reason) in production or real world scenario.