Skip to main content

Publishing Resources in Active Directory


What Resources can be published in Active Directory

When you make Active Directory objects available to users, you are publishing the Active Directory resource. The resources that can be published in Active Directory include the Active Directory resources listed below:
  • User objects
  • Computer objects
  • Printer objects
  • Folders and files
  • Network services
The two primary published objects are printers and shared folders. Publishing information on shared network resources such as printers, folders, and files; eases the process of users locating these resources. Having resource information in Active Directory makes it easy to search for, and find a particular resource. You can use the Active Directory Users and Computers console to publish information on shared folders and printers in Active Directory.publishing resources in active directory Publishing Resources in Active Directory
With Windows 2000 Active Directory, Windows 2000 network printers were automatically published in Active Directory. What this meant was that you only had to manually publish information on Windows NT printers in Active Directory. Windows Server 2003 printers are also automatically published in Active Directory. In fact, when you share printers on the network, they are automatically published in Active Directory. If you do not want to publish a particular printer in Active Directory, you have to access the Properties dialog box of that printer, click the Sharing tab, and then uncheck the List In The Directory checkbox.
Some information on network users is also automatically published after they are added using the Active Directory Users and Computers console.
When network services are published in Active Directory, you can administer the particular service through the utilization of the Active Directory Sites and Services console. This strategy ensures that you can perform administrative tasks for the network service, regardless of the computer on which the service is running, or its location in the network.
There are two categories of information on services that are typically published in Active Directory. Binding information makes it possible for clients to access those services that have no well-known bindings. By publishing binding information for certain services, the system is able to automatically create connections with these particular services. Configuration information is used by client applications. When you publish this type of service information, you are basically ensuring that each client in the domain can access this information.

How to publish a shared folder in Active Directory

  1. Open the Active Directory Users And Computers console
  2. In the left console tree, expand the domain that you want to place the shared folder in, which you want to publish in Active Directory.
  3. Right-click the container or OU to which you want to add the shared folder, and click New, and then Shared Folder from the shortcut menu.
  4. When the New Object-Shared Folder dialog box opens, enter a name for the shared folder in the Name box.
  5. Enter the UNC path to the share in the Network Path box.
  6. Click OK

How to publish a printer in Active Directory

  1. Open the Active Directory Users And Computers console
  2. In the left console tree, expand the domain that you want to place the Windows NT printer in, which you want to publish in Active Directory.
  3. Right-click the container or OU to which you want to add the printer, and click New, and then Printer from the shortcut menu.
  4. When the New Object-Printer Folder dialog box opens, enter the UNC path to the printer in the Network Path Of The Pre-Windows 2000 Print Share box.
  5. Click OK.

How to publish a network service (Public Key Services) in Active Directory

  1. Open the Active Directory Sites And Services console.
  2. In the left console tree, select Active Directory Sites And Services, click Services, Public ey Services, and then Certificate Templates.
  3. You can now set permissions for any certificate template by opening the properties of the certificate template, clicking the Security tab, and then setting the necessary security permissions.
  4. Click OK. Changes are only valid for certificate templates within the current domain.

How to search for a printer published in Active Directory

  1. From the Start menu, click the Search option, and then click Printers, Computers, Or People
  2. Select A Printer On The Network
  3. Enter the name of the printer in the Name box, or the location of the printer in the Location box, or the model of the printer in the Model box.
  4. If you want to define specific features, click the Features tab.
  5. The Advanced tab contains additional parameters that you can specify for the printer.

How to use the Active Directory printer location tracking feature to find printers in large enterprises

The printer location tracking feature is only useful for searching for printers in large enterprises. With printer location tracking, the location of the printer is stored in Active Directory. This enables users to find printers by specifying the name or location of the printer, as well as a few features.
The following requirements have to be met if you want to use printer location tracking.
  • You have to install Active Directory on the network
  • More than one site has to be configured, or at least two subnets need to exist.
  • Each site has to exist on a different subnet
  • All client computers should be capable of querying Active Directory
  • The subnet which your clients are going to need to access must have individual subnet objects in Active Directory.
  • A printer naming convention has to be defined.
  • When the printers are published in Active Directory, the Location field has to be enabled.
Use the steps below to enable printer location tracking
  1. Open the Active Directory Sites and Services console.
  2. From the sites folder, right-click the site which you want to work with, and click Properties from the shortcut menu.
  3. Select the Location tab.
  4. Enter the location for the site. You can alternatively click the Browse button to choose the location.
  5. Click OK.
  6. Repeat Step 2 – 5 for each site and subnet.
  7. Open the Active Directory Users and Computers console.
  8. Right-click the domain that you want to enable printer location tracking for, and click Properties from the shortcut menu.
  9. Select the Group Policy tab.
  10. Choose the policy which should be edited, and click Edit
  11. Expand Computer Configuration, Administrative Templates, and then Printers
  12. Double-click Pre-Populate Printer Search Location Text, and choose Enabled.
  13. Click OK.
  14. Open the Printers And Faxes folder for the print server.
  15. Right-click the initial printer and then select Properties from the shortcut menu.
  16. Enter the appropriate information in the Location box.
  17. Repeat Step 15 – 16 for each printer in Active Directory.

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...