Editing GSTN - Directory services DNS PRINT DHCP (section)

= How to Handle Situations Where a DC with FSMO Roles Is Offline  =

There are three situations to distinguish: 

1. The downtime is planned and the DC will come back soon (reboot, hardware replacement, etc.): 

<div style="margin-left:1cm;margin-right:0cm;">In this case, you have to decide, to temporarily transfer the roles to a different DC or be aware of the effects during the downtime. </div>

2. The DC should be demoted: 

<div style="margin-left:1cm;margin-right:0cm;">Transfer the roles to a different DC, before you demote. </div>

3. The DC is offline because of a problem: 

<div style="margin-left:1cm;margin-right:0cm;">1. Don't panic! </div>

<div style="margin-left:1cm;margin-right:0cm;">2. Depending on the kind of role(s) that were on the DC, the consequences may be different. Make sure that you find out which roles are affected and what it means for your forest. See [https://wiki.samba.org/index.php/Transfering_/_seizing_FSMO_roles#The_seven_FSMO_roles The seven FSMO roles]. </div>

<div style="margin-left:1cm;margin-right:0cm;">3. Try repairing the broken DC and connect it to the network again. But never restore it from a backup, if at least one DC in the domain is still working. The replication could mix up your directory! </div>

<div style="margin-left:1cm;margin-right:0cm;">4. If there is no chance to get the DC back again, seize the roles on a remaining DC and [https://wiki.samba.org/index.php/Demote_a_Samba_AD_DC demote the broken one]. </div>

<div style="color:#00000a;">To check FSMO roles hit below command.</div>

''<nowiki># /usr/local/samba/bin/samba-tool fsmo show</nowiki>''

== Seizing a FSMO Role  ==

* <div style="margin-left:1.247cm;margin-right:0cm;">Log on to the DC, that should be the new owner of the role you want to transfer. </div>

* <div style="margin-left:1.247cm;margin-right:0cm;">Seize the role to the current DC, by executing the following command: </div>



''<nowiki># /usr/local/samba/bin/samba-tool fsmo seize --role=all</nowiki>''

Attempting transfer...

Transfer unsuccessful, seizing...

FSMO seize of '...' role successful* <div style="margin-left:1.247cm;margin-right:0cm;">Ensure that the role was transferred ('samba-tool fsmo show'). </div>

* <div style="margin-left:1.247cm;margin-right:0cm;">Make sure, that the old DC is never connected to the network again! </div>







# 
## '''SAMBA integrated CUPS ( Print Server )'''[[Image:GSTNDIRECTORY31.png]]



A print server accepts print jobs from network computers, queues them locally and then sends them to the appropriate printers. As well as having domain and file service capabilities, Samba can also act as a MS Windows compatible print server. While Samba provides the interface to Windows/SMB machines, CUPS or LDP is used by Samba to send print jobs to the devices.

CUPS provides a mechanism that allows print jobs to be sent to printers in a standard fashion. The print-data goes to a scheduler which sends jobs to a filter system that converts the print job into a format the printer will understand. The filter system then passes the data on to a backend—a special filter that sends print data to a device or network connection. The system makes extensive use of PostScript and rasterization of data to convert the data into a format suitable for the destination printer.

The CUPS scheduler implements Internet Printing Protocol (IPP) over HTTP/1.1. A helper application (cups-lpd) converts Line Printer Daemon protocol (LPD) requests to IPP. The scheduler also provides a web-based interface for managing print jobs, the configuration of the server, and for documentation about CUPS itself.

CUPS can process a variety of data formats on the print server. It converts the print-job data into the final language/format of the printer via a series of filters. It uses MIME types for identifying file formats.

The backends are the ways in which CUPS sends data to printers. There are several backends available for CUPS: parallel, serial, and USB ports, cups-pdf PDF Virtual Printing, as well as network backends that operate via the IPP, JetDirect (AppSocket), Line Printer Daemon ("LPD"), and SMB protocols.

CUPS integrated with SAMBA supports multiple end user operating systems – e.g. Linux all flavors (Desktop OS and Server OS, Windows 7 and higher, Windows server 2003 and higher, Mac OS.

== SMB.CONF Configuration. ==

'''To integrated '''CUPS with samba i m'''ade below entries in smb.conf.'''


[[Image:GSTNDIRECTORY32.png]]


'''CUPS web-based administration interface'''

On all platforms, CUPS has a web-based administration interface that runs on port 631. It particularly helps the need to monitor print jobs and add print queues and printers remotely. This interface is with an enhanced administration interface that allows users to add, modify, delete, configure, and control classes, jobs, and printers. It Supports reports/ monitoring, Auditing and tracking of print queues . It will also do the centralized allocation /DE-allocation of Network printers to the users.

[[Image:GSTNDIRECTORY33.png]]

'''CUPS quotas'''

CUPS supports page and size-based '''quotas''' for each printer. The quotas are tracked individually for each user, but a single set of limits applies to all users for a particular printer. CUPS '''logsevery page''' that is printed on a system to the ''page_log'' file. Page logging is only available for drivers that provide page accounting information, typically all PostScript and CUPS raster devices. Raw queues and queues using third-party solutions such as Foomatic generally do not have useful page accounting information available.

Structure at GSTN : The HP Laserjet Pro M202dw printers act as print servers and authenticate against the Samba AD.


Quota can be deploye only from command line. Below are the commands to deploy quota:

'''<nowiki># lpadmin -p ProLaserJet -o job-quota-period=604800 -o job-k-limit=1024 </nowiki>'''

This sets a limit of a file size of 1 MB (added-up) for each user on the existing printer "''ProLaserJet''" during one week.

'''<nowiki># lpadmin -p ProLaserJet -o job-quota-period=604800 -o job-page-limit=100 </nowiki>'''

This sets a limit of 100 pages (added-up) for each user on the existing printer "''ProLaserJet''" during one week.

'''<nowiki># lpadmin -p ProLaserJet -o job-quota-period=604800 -o job-k-limit=1024 -o job-page-limit=100 </nowiki>'''

>>A day is 60x60x24=86400, a week is 60x60x24x7=604800, and a month is 60x60x24x30=2592000 seconds.)

This sets a combined limit of 1 MB (added-up) and 100 pages (added-up) for each user of existing printer "''ProLaserJet''" during one week. Whichever limit is reached first will take effect.

<div style="color:#00000a;">[[Image:|top]]</div>