Powered by Blogger.

Wednesday, 13 November 2013

Windows 8, good practices, but, so far, not everyone's Cup of tea. It is not with the older version of Windows or Linux, is also not compatible with it to access some files throughout the system. Here's how sharing network of old, but trust settings share a folder.
Describes the homegroup in Windows 8, setting up a home network has become much easier. Although it is a large and comfortable features, Windows 8 computers, she unfortunately cannot use an earlier version of Windows or Linux on any compulsory recourse to the usual network share settings. This is the irony, such return becomes a little more complicated, which tend to prevent the user with an error message after another, why even a simple file transfer is impossible. Not need to accumulate your brain in these matters, but here is how you can make the function of sharing in three steps and keep track of your shared folder.

Please make sure you use a NAT router (applicable to almost any router) as access to the Internet, if you want to use this tool. Otherwise, you can release your documents to your local network, not only for the entire Internet. In addition, it is important to verify that all computers on the network are using the same working group. It may also be interesting: how to create a family group in the Windows 7 and 8




As a general rule, Windows Firewall blocks Windows 8, the application will work correctly. You can add an exception and let go of the firewall software to resolve this problem.


Search for "firewall" in the Windows 8 Start menu. Click on the Settings option.


Select Windows Firewall from the options that appear in the top left.


Click on "allow an app or feature through Windows firewall in the Windows Firewall window


Click "Change settings" in the next window. Click "Allow another app..." in the bottom right corner.


A superscope is running Windows Server 2008, you can create and manage the DHCP Microsoft Management Console (MMC) snap-in using the Dynamic Host Configuration Protocol (DHCP) server management functions. Through the use of the Super scope, can be used as a single administrative entity for grouping multiple scopes. To use this feature, DHCP server, you can:

  • Multiple logical IP networks using a single physical network segment (such as a single Ethernet LAN segment) to support DHCP clients. When used on each physical subnet or network when more than one logical IP network, such configurations are often called multinets.


  • Support remote DHCP clients are located on the far side of DHCP and BOOTP relay agents (network on the other side of the relay agent uses multinets).

In multinet configurations, you can use scopes global DHCP to group and to start on the network uses individual scope of IP addresses ranges of. In this way, the DHCP server can initiate and provide leases more scope to clients on a single physical network.
Superscopes can resolve multinets, including cases, certain types of DHCP deployment issues:
Pool of addresses available for the currently active scope is nearly depleted and need to add multiple computers to the network. Original scope includes the full addressable range for a single IP network address specified class. You will need to use a different range of IP addresses to extend the address space on the same physical network segment.

Clients must be migrated to a new scope (for example to renumber on an existing active scope to a new scope that contains another range of IP addresses for the beaches of current IP addresses that are used in the network).

You want to use two DHCP servers on the same physical network segment to manage separate logical IP networks.

Non-routed DHCP server (Before Superscope):

Small local area network (LAN) with one DHCP server supports a single physical subnet, subnet a. In this configuration is limited to the same physical subnet DHCP Server client leased addresses.
The following illustration shows how this sample network to its original state. Now that you have added no superscopes and scope of individual, range 1, used a. service all DHCP clients on the subnet.
In the post "how to install DNS on Windows Server 2012?”  explains installing DNS, and now, I said management of the DNS server.
If you install DNS on the domain controller, administrative work so little, because with Active Directory is integrated with DNS.
DNS clients to automatically update their DNS records, you save a connection's address in DNS is selected (the default setting), or your DHCP servers to register DNS records on behalf of DNS clients. Therefore, most of the time, it is very easy to management of DNS. Otherwise, if you want to manually set up, took note of those programs.

1. Press Windows Key + R, execute dnsmgmt.msc
2. On DNS Manager window, right-click your server and click New Zone
3. On wizard, click on Next. On Zone Type window, select Primary zone (because the first zone must be         primary), and check Store the zone in Active Directory (it is selected by default). Then click Next
4. On Active Directory Zone Replication Scope page, select the default option of To all DNS servers               running on domain controllers on this domain : CyrusBesharat.local, click Next then
5. Be sure to select Forward lookup zone as the default option, and click Next
6. Type CyrusBesharat for zone name, then click on Next
7. Check the radio button of Allow only secure dynamic updates (recommended for Active Directory),             click onNext, then Finish to close the wizard
8. Now you should add records to DNS server, so on DNS manager, expand SERVER1, Forward                 Lookup Zones, then right click  CyrusBesharat, and select New Host (A or AAAA)…
9. On New Host window, type the name of one of your computers, for example Server2, and below IP           address type its IP address like 10.10.10.2. And click Add Host, then confirm OK and close the                 window.


BitLocker is probably one of the single most important advance in computing security. It's all serious business now is to use the Windows system requirements. Read this article to understand BitLocker.
If you have Windows 8, you'll notice, will try to enable BitLocker with the TPM, which is a property of the processor. Possibility of marrying security encryption software and processor device is perfect.
What would happen if, but your notebook computers/Tablet PCs do not have a TPM-compatible processor? If we try, awe can see this message.


Here’s how to enable BitLocker for windows 8 in these cases.
In your windows 8, call the gpedit.msc.


in the group policy manager navigate to Computer Configuration/Administrative Templates/Windows Components/BitLocker Drive Encryption/Operating System Drives. Once there, double-click the option Require additional authentication at startup


Choose the option Enabled and in the options pane select the checkbox Allow BitLocker without a compatible TPM.


That’s it. Your device is now ready to be encrypted with BitLocker. Right-click your disk and the option to Turn on BitLocker will be available.


You need to keep a USB stick to save the credentials BitLocked. Can also be saved to a file and upload the files to your preferred storage location.




Tuesday, 12 November 2013

The domain name system (DNS) is used to connect to any Internet resource naming system. Convert DNS domain name, that is in the IP address of the Internet resource of mankind, found all over the world makes more sense. Every time when using an IP address, DNS name translation the corresponding IP address. A forward lookup zone host name to IP address. When requested by a from a particular host computer's IP address, the query directly in the search box in order to get results. In contrast, the reverse of the corresponding image area contains the host name IP address. When a computer requests to specific IP addresses when the host name, the reverse zone being queried to get answers.

What is forward lookup zone?

A forward lookup zone contains the host name and IP address for the image. When a computer requests by providing a host name IP address (that is, the more user friendly interface), a forward lookup query to find the IP address for a given host name. For example, when you type in your browser, forward lookup zones will return the IP address 157.166.255.19, this is actually the IP address of the Web site. When a forward lookup is sent to the DNS server, DNS host name of the server provided by the search request associated with an a type resource record. A resource type can be used to point to a static IP address of the DNS records of the domain name and the host name. If the DNS server finds a match type resource record, it will be returned to the client, otherwise it forwards the query to another DNS server.

What is reverse lookup zone?

A forward lookup zone contains the host name and IP address for the image. When a computer requests an IP address through the provision of a host name (that is, more user-friendly interface), the forward lookup zone of the query to find the IP address for the given host name. For example, when you type in your browser, forward lookup zones will return the IP address 157.166.255.19, this is actually the IP address of the Web site. When a forward lookup is sent to the DNS server, the search request to the provided host name and the DNS server resource records associated with a type. Types of resources can be used to refer to a static IP address of the DNS records of the domain name and host name. If the DNS server locates a matching the type of resource record, it will be returned to the client, otherwise it will forward the query to another DNS server.
Step by Step Instructions:

Perquisites:

Windows server 2012 has been installed.

Workarounds for known bugs:

There are no known bugs for this feature at this time.

Installing IIS 8 default setting:

To install IIS 8, use the following steps:

  • Open Server Manager.
  • Under Manage menu, select Add Roles and Features:


Select Role-based or Feature-based Installation


Select the appropriate server (local is selected by default), as shown below:


Select Web sever (IIS):


No additional features are needed for IIS, so click Next:


Click Next


Custom IIS, installation or accept the default settings have been selected and then click Next:


Click Install 



When the IIS installation completes, the wizard reflects the installation status:


Considering that Windows 2008 "oldschool" and known as the 2003 Terminal Services is extending a wealth of Web services, is now available in the design based on the HTTP/HTTPS servers and new features in Terminal Services. In combination with remote desktop gateway can also be safely released on WWW and session host server application isolation in non-public network address. All Terminal Server service is now called remote desktop services path

To enable the RD (remote desktop) services in General, and 2 ways, the "quick launch" and "standard deployment". Are there 2 types of RD session available services, virtualization or virtual desktop infrastructure (VDI). In this blog, I focused on deployment, which means hosting and server virtualization RDS application publishing Terminal Server session.

Quick start straightforward and rapid deployment of services, and configure a standard application key can be used to set up the lab/demo environment:


Standard Deployment



In the following steps depending on your connection broker, Web access and session host server deployment options. In a single-server deployment, you can specify a single server all roles:






I do not allow “user profile disks”  but in case this is required, select “Enable” and set the required NTFS permissions on folder.


When session collection group is created you can start with configuration of the apps you want to publish.





If you want to use Microsoft remote desktop services give users access to remote desktop and applications, you will need to know how to install it.

Install office remotely (RDS) Microsoft services, you must first understand its various components. A part of this series, I explained that the RDS role and each of them will not. Broken how to install the front remote desktop services, view us the C:

Remote Desktop (RD) Virtualization Host:

  • Host Virtual Machine
RD Session Host:

Hosts RemoteApp published applications or session-based desktops

RD web Access (mandatory):

Allows users to access programs RemoteApp and desktop connection through the start menu on Windows 8, Windows 7 or via Web browser

Choosing an installation method:

You can install all the RDS roles from a single server using the Remote Desktop Services tool via the new Server Manager in Windows Server 2012. Here's how:

Open the Server Manager Console and select option three: "Add other servers to manage"
Add the servers you want to deploy Remote Desktop Services to
In the Server Manager Console, select option two: "Add roles and features"
Select "Remote Desktop Services installation"
Then, install Remote Desktop Services in one of two ways:

Standard deployment. With this method, you deploy Remote Desktop Services roles to multiple servers. For typical production deployments, choose a standard deployment that allows you to install each role service separately on separate servers if desired.

If you select a Standard deployment, you will be prompted to choose which server(s) you would like to deploy the RD role services to. For a typical RDS installation where high availability and security are important, you should deploy each component to a dedicated server.

Quick Start. With Quick Start, you install Remote Desktop Services role services onto a single server. This route is usually reserved for proof-of-concepts or very small deployments.

If you choose Quick Start, you will be asked for one server to deploy the RD roles to. 
Domain is unable to communicate with the other domain by default this means x in one domain cannot access any resources, is part of the domain y. Before you configure the trust relationship

  • admin not in domain y user any document or printer
  • Domain y user cannot sit at the workstation is part of a domain, x and login

After you have defined a relationship of trust,

  • The domain y user can sit at a workstation, is part of a domain x and log on to their domain y (it will appear in the domain drop-down list box)
  • Administrator domain x domain y that can be granted to any user rights, file and print resources

Domain y user is included in the Everyone group of the domain x
X is the trusting domain in the example above, and y is the trusted domain. In addition more than a one-way trust relationship is, that while the domain y user x can use domain resources, y domain x users cannot use domain resources. A two-way relationship allows access to a resource to each of the other domains (if given).

Configure domain trust relationship is the basis of the first y allows the domain to trust it, and then configure the x  trusts domain a domain:


  1. Log onto domain y as Administrator
  2. Start User Manager for Domains (Start - Programs - Administrative Tools)
  3. Select "Trust Relationships" from the Policies menu
  4. Click the Add button to the Trusting Domains box
  5. Enter the name of the domain you want to be able to trust you, i.e. domain x
  6. You can type a password in the Initial Password and Confirm Password, however this is only used when the trust relationship is started. You can leave it blank Click OK to complete the addition
  7. Close the Trust Relationship dialog box
  8. Log off of domain y and logon onto domain x as Administrator
  9. Start User Manger for Domains, and choose "Trust Relationships" from the Policies menu
  10. Click the Add button to the Trusted Domains box
  11. Enter the name of domain y and the password if one was configured in step 6
  12. Click OK and close the User Manager for Domains application.
  13. Domain x now trusts domain y

In the Active Directory of big improvement over its predecessor in NT4 in which the AD is one of trust relationships in a multi-domain environment.
In Windows 2000 and in Windows Server 2003 Active Directory, you have enabled, by default, automatically creates certain trust relationships: parent and create it, and multiple domain trees in a forest root domain two-way transitive trust between the bottom of the two-way transitive trust relationships between all domains. Two-way trust relationship means users in domain a can access resources in domain b uses the same trust relationships, allowing users to access a domain b. resources in the domain that has greatly simplified compared to NT4, you need to create and manage a separate trust relationships (one-way trust) in each direction if you need to configure access the trust of both sides. Transitive trust relationship means that if domain a trusts domain b, and domain b trusts domain c, then an implicit trust relationship between domain a and domain c automatically; there is no need to manually create a third trust relationships. Therefore, if the Active Directory domain has many subdomains, all those subdomains are implicit trust relationships, because they all have a trust relationship with that single parent domain. Similarly, contains multiple domain trees in the forest, each all subdomains of the domain tree can access resources in the other tree by default, each domain tree's root domain trusts between the transitive nature.

NT4 large improvements over its predecessors in Active Directory in which the AD is one of managing trust relationships in a multi-domain environment.
In Windows 2000 and in Windows Server 2003 Active Directory, you have enabled, by default, automatically creates a trust relationship: parent and create it, and multiple domain trees in a forest bottom two-way transitive trust between the root domains of all two-way, transitive trust relationships between the child domain. Two-way trust relationship means users in domain a can access resources in domain b, using the same trust relationships, allowing users to access a domain b. resources in the domain that greatly simplifies matters compared to NT4, you need to create and manage a separate trust relationships (one-way) in each direction if you need to configure access to confidence on both sides. Transitive trust relationship means that if domain a trusts domain b, and domain b trusts domain c, then an implicit trust relationship between domain a and domain c automatically; there is no need to manually create a third trust relationships. Therefore, if the Active Directory domain has many subdomains, all those subdomains are implicit trust relationships, because they all have a trust relationship with that single parent domain. Similarly, contains multiple domain trees in the forest, each all subdomains of the domain tree can access resources in the other tree by default, each domain tree's root domain trusts between the transitive nature.

This is by introducing improved on Windows Server 2003 cross-forest trusts. The advanced features of Active Directory is available, if the forest is at the Windows Server 2003 forest functional level, this means that on those two all the domain controllers in all domains in the forest are running Windows Server 2003, you manually change to the new forest functional level. Across forest trust is can passed of this meant with in forest a, in the of each domain will and each domain in the forest b. has implicit type trust relationship this what passed sexual does not meant with for across Directory forest trust (and causes this often confusion) is: If you has across Directory forest trust relationship forest a, and forest b and forest b and forest c of second times across Directory forest trust, forest a, and forest c not exists trust relationship you will needs created second a across Directory forest trust relationship forest a, and forest c allows such occurred. Cross-forest trusts can be one-way or two-way, and you will build trust between the forest root domain for each forest.

2012, remote desktop services, Microsoft has been added with the server has the possibility of rapid-start the deployment on a single server.

This deployment is a proof of concept, test or an environment of small size, you will only need a managed shared office (RDSH) Server RDS is ideal for rapid deployment.

Deploy to a server roles:

  • Connection - Broker RD
  • RD Web Access
  • Host login

The only role that is installed is RD licensing server, you will need to manually implement this role.
The rapid deployment of home also configures a set example of RemoteApp applications (paint, calculator, Wordpad)
The following guide will explain how to configure the deployment to begin:
In Server Manager, click Add features.


Click on "Next "

Select "Remote Desktop Services Installation"


Select Quick Start for the Quick Start deployment.


Select "Session-based desktop  deployment"


Select the (local) Server you want to deploy to


Select ‘ Restart the destination server automatically if required’ and then click on ‘Deploy’

The roles will now be installed in the selected server.


The Server will reboot during the deployment. The setup will continue after the server has been restarted.


All roles have now been installed successfully, click ‘Close’ to continue


The server administrator can see now services desktop remotely role appears to the left. Select the function to display a summary of the RDS deployment. RD role and functions of the gateway licences which have a more ' green ' because these functions have not been implemented by the fast start deployment.


You need to deploy RD licensing role, if you plan to use this server as a production or need more then two users to connect to a proof of concept or testing. Remote Desktop services client access license (CAL) is required on a per-user or per-device basis can purchase client access licenses.

The Quick Start has already created a RemoteApp collection with Calculator, Paint and Wordpad.


You can remove or add the application's environment.

When you connect to the RD Web access server, you will be able to see and choose to publish RemoteApp applications.

Note: Please make sure that you start a RemoteApp application client devices can solve the RDS session host server's FQDN. If you can only get the NetBIOS host name for the server's IP number, you will receive an error message.