<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-7937478262084849847</id><updated>2024-10-24T06:23:56.095-07:00</updated><category term="Debian"/><category term="Comandi Linux"/><category term="Exchange 2010"/><category term="Comandi Windows"/><category term="Webmin"/><category term="Wordpress"/><category term="apache2"/><category term="php5"/><category term="t-sql"/><category term="451 4.4.0 DNS query failed"/><category term="BlackBerry Enterprise Server"/><category term="Dynamics"/><category term="Hardened PHP"/><category term="Linux"/><category term="Oracle VM"/><category term="OracleVm re-Register host"/><category term="Server database Aruba down 20 agosto 2011"/><category term="Sysprep"/><category term="Update win2008 come rimuoverli"/><category term="VSFTPD"/><category term="Vmware - HA initiated a failover action in cluster"/><category term="W3WP High Memory Usage"/><category term="active directory"/><category term="adsense"/><category term="architettura mysql"/><category term="aruba database"/><category term="avviare liferay"/><category term="backup active directory"/><category term="cartelle condivise"/><category term="connessioni di rete"/><category term="crm"/><category term="database"/><category term="dhcp"/><category term="email router"/><category term="esecuzione"/><category term="fedora"/><category term="file bin"/><category term="ftp"/><category term="google"/><category term="gruppo di ditribuzione"/><category term="linked server"/><category term="mysql"/><category term="ntpdate"/><category term="plesk"/><category term="pool di nat"/><category term="proftpd"/><category term="qmail"/><category term="reservation"/><category term="restore"/><category term="samba"/><category term="server collegati"/><category term="sicurezza"/><category term="smtp"/><category term="spam control rule"/><category term="spamfilter"/><category term="sql server"/><category term="sqlserver"/><category term="suhonin"/><category term="ubuntu"/><category term="virtualhost"/><category term="win2008"/><title type='text'>Administrator skill</title><subtitle type='html'>Appunti e articoli tecnici per tecnici, system administrator, sistemisti in ambienti Linux e Microsoft.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default?start-index=26&amp;max-results=25&amp;redirect=false'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>37</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-3948101659204974744</id><published>2012-01-17T03:45:00.000-08:00</published><updated>2012-01-17T03:45:00.888-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="linked server"/><category scheme="http://www.blogger.com/atom/ns#" term="server collegati"/><title type='text'>Come creare server collegati sql server 2008</title><content type='html'>Procedura per aggiungere server collegati, testate da sqlserver 2008 a sqlserver 2008&lt;br /&gt;&lt;ol&gt;
&lt;li&gt;Go to “Server Objects” of the database server where the linked 
server will be added and right click on “Linked Servers”. Select “Add 
New Linked Server”.&lt;/li&gt;
&lt;li&gt;In the “General” tab,  add a name for the new linked server in the “Linked Server” field.&lt;/li&gt;
&lt;li&gt;Select “Other data source”and for “Provider” select “Microsoft OLE DB for SQL Server”&lt;/li&gt;
&lt;li&gt;For “Product Name” type in “SQLOLEDB”&lt;/li&gt;
&lt;li&gt;In the “Data Source” field, enter the IP address of the server to be linked&lt;/li&gt;
&lt;li&gt;“Catalog” is the name of the database on the linked server and is optional&lt;/li&gt;
&lt;li&gt;Go to the “Security” tab and select “Be made using this security context”. Type in the remote login and credentials&lt;/li&gt;
&lt;/ol&gt;</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/3948101659204974744/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2012/01/come-creare-server-collegati-sql-server.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3948101659204974744'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3948101659204974744'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2012/01/come-creare-server-collegati-sql-server.html' title='Come creare server collegati sql server 2008'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-2735637735132758715</id><published>2011-09-22T08:55:00.000-07:00</published><updated>2011-09-22T08:55:51.468-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="451 4.4.0 DNS query failed"/><title type='text'>451 4.4.0 DNS query failed</title><content type='html'>The Problem &lt;br /&gt;
&lt;br /&gt;
For whatever reason, Exchange (and DNS) is hyper sensitive to a DNS domain that provides a bogus response (say one Name Server is healthy, the other is not). It appears to be an issue where we need to wait until the DNS TTL expires or, we perform the &#39;solution&#39; below. This is a temporary measure as we work with the end user domain, to find out what is going on with their DNS (in both cases, after flushing DNS locally and my AD DNS server, I would get a different DNS NS result, and sometimes an MX record, sometimes not … strange, but their problem). However, Exchange 2007 seems to be especially sensitive to this…&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;For example, with the domain below, here is the error I&#39;ve been experiencing (in the Exchange 2007 Queue…) – 451 4.4.0 DNS query failed&lt;/b&gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
The Solution &lt;br /&gt;
&lt;br /&gt;
Or should I say, the workaround. The solution is contact the destination DNS/domain provider and have them fix their problems (though perhaps a future fix from Microsoft/Exchange will resolve this, or maybe they have and I&#39;m somehow unable to stumble across the answer). However, the workaround is…&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
■Flush your Active Directory DNS Cache (to do this, you&#39;ll need to have &#39;advanced&#39; turned on, the View option in DNS)&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
On your Exchange 2007 Server(s), flush your local DNS Cache &lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
IPCONFIG /FLUSHDNS &lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
For me, repeatedly, when I click &#39;retry&#39; in the Exchange 2007 Message queue, the message leaves immediately. Sure enough, a few hours later I have a crap record but it does at allow the messages to flow. Now to get the target domain/DNS provider to cooperate and recognize they have a problem, of some sort…&lt;br /&gt;
&lt;b&gt;&lt;br /&gt;
Controlla anche connettore d&#39;invio in trasporto Hub, nella scheda rete, che sia flagggata la casella Utilizza le impostazioni di ricerca dns esterno nel server di trasporto&lt;/b&gt;</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/2735637735132758715/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/09/451-440-dns-query-failed.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/2735637735132758715'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/2735637735132758715'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/09/451-440-dns-query-failed.html' title='451 4.4.0 DNS query failed'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-31588719490350298</id><published>2011-08-26T03:09:00.000-07:00</published><updated>2011-08-26T03:09:30.644-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Sysprep"/><category scheme="http://www.blogger.com/atom/ns#" term="win2008"/><title type='text'>Sysprep in windows 2008</title><content type='html'>Con il tool fornito da Microsoft sysprep, che in Windows 2008 è disponibile nella directory C:\Windows\system32\sysprep, si effettua la procedura per il cambio del SID.&lt;br /&gt;
&lt;br /&gt;
Per evitare possibili imprevisti dovuti ad un’errata procedura, gli step raccomandati da seguire sono due:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. Aprire il Command Prompt con diritti di Administrator&lt;br /&gt;
2. Eseguire il comando:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /shutdown&lt;br /&gt;
</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/31588719490350298/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/08/sysprep-in-windows-2008.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/31588719490350298'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/31588719490350298'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/08/sysprep-in-windows-2008.html' title='Sysprep in windows 2008'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-4296819616900215989</id><published>2011-08-25T08:55:00.003-07:00</published><updated>2011-08-25T08:55:18.864-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Update win2008 come rimuoverli"/><title type='text'>Rimuovere download Microsoft Update da Win2008</title><content type='html'>1. Open Start &gt;&gt; Run or press window key + r&lt;br /&gt;
 &lt;br /&gt;
2. Type “services.msc” (without quotes) and Click OK , this will open services window.&lt;br /&gt;
 &lt;br /&gt;
3. Right click on Automatic Updates Service and select Stop.&lt;br /&gt;
 &lt;br /&gt;
4. After the service is stopped, press window key + r&lt;br /&gt;
 &lt;br /&gt;
5. Type “%windir%\SoftwareDistribution” (without quotes) and press enter.&lt;br /&gt;
 &lt;br /&gt;
6. Open the Download folder and delete all contents of the Download folder.&lt;br /&gt;
 &lt;br /&gt;
7. Close the window, press Window Key + r ( or Open Start &gt;&gt; Run )&lt;br /&gt;
 &lt;br /&gt;
8. Type “services.msc” (without quotes) and Click OK&lt;br /&gt;
 &lt;br /&gt;
9. Right click on Automatic Updates Service and select Start.&lt;br /&gt;
 &lt;br /&gt;
10. That’s it Done&lt;br /&gt;
</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/4296819616900215989/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/08/rimuovere-download-microsoft-update-da.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/4296819616900215989'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/4296819616900215989'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/08/rimuovere-download-microsoft-update-da.html' title='Rimuovere download Microsoft Update da Win2008'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-4987069469726633897</id><published>2011-08-21T14:54:00.000-07:00</published><updated>2011-08-21T14:54:06.912-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="OracleVm re-Register host"/><title type='text'>OracleVm re-Register host</title><content type='html'>Hi Honza,&lt;br /&gt;
&lt;br /&gt;
just tried it:&lt;br /&gt;
&lt;br /&gt;
Before:&lt;br /&gt;
# /opt/ovs-agent-latest/utils/repos.py -l&lt;br /&gt;
[ * ] b2638dcd-fa49-4646-a7da-83e91e7e26c4 =&gt; /dev/hdb1&lt;br /&gt;
# du /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4/running_pool&lt;br /&gt;
2316896 /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4/running_pool/30_OEL1&lt;br /&gt;
&lt;br /&gt;
Then:&lt;br /&gt;
# /opt/ovs-agent-latest/utils/cleanup.py&lt;br /&gt;
This is a cleanup script for ovs-agent.&lt;br /&gt;
It will try to do the following:&lt;br /&gt;
&lt;br /&gt;
*) stop o2cb heartbeat&lt;br /&gt;
*) offline o2cb&lt;br /&gt;
*) remove o2cb configuration file&lt;br /&gt;
*) umount ovs-agent storage repositories&lt;br /&gt;
*) cleanup ovs-agent local database&lt;br /&gt;
&lt;br /&gt;
Would you like to continue? [y/N] y&lt;br /&gt;
Cleanup done.&lt;br /&gt;
&lt;br /&gt;
No Repos anymore:&lt;br /&gt;
# /opt/ovs-agent-latest/utils/repos.py -l&lt;br /&gt;
&lt;br /&gt;
Create New:&lt;br /&gt;
/opt/ovs-agent-latest/utils/repos.py -n /dev/hdb1&lt;br /&gt;
[ NEW ] b2638dcd-fa49-4646-a7da-83e91e7e26c4 =&gt; /dev/hdb1&lt;br /&gt;
/opt/ovs-agent-latest/utils/repos.py -r b2638dcd-fa49-4646-a7da-83e91e7e26c4&lt;br /&gt;
&lt;br /&gt;
Not mounted yet:&lt;br /&gt;
# df -k&lt;br /&gt;
/dev/hda2 4466156 930456 3305168 22% /&lt;br /&gt;
/dev/hda1 101086 45803 50064 48% /boot&lt;br /&gt;
tmpfs 296536 0 296536 0% /dev/shm&lt;br /&gt;
&lt;br /&gt;
Initializing:&lt;br /&gt;
/opt/ovs-agent-latest/utils/repos.py -i&lt;br /&gt;
&lt;br /&gt;
Mounted!:&lt;br /&gt;
# df -k&lt;br /&gt;
Filesystem 1K-blocks Used Available Use% Mounted on&lt;br /&gt;
/dev/hda2 4466156 930468 3305156 22% /&lt;br /&gt;
/dev/hda1 101086 45803 50064 48% /boot&lt;br /&gt;
tmpfs 296536 0 296536 0% /dev/shm&lt;br /&gt;
/dev/hdb1 33551720 6040232 27511488 19% /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4&lt;br /&gt;
&lt;br /&gt;
And data still there:&lt;br /&gt;
# du /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4/running_pool&lt;br /&gt;
2316896 /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4/running_pool/30_OEL1&lt;br /&gt;
&lt;br /&gt;
However as noted above: The /OVS link to the /var/ovs/mount point will be created when you register the server with OVM Manager.&lt;br /&gt;
All additional data will be left on the device.&lt;br /&gt;
</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/4987069469726633897/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/08/oraclevm-re-register-host.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/4987069469726633897'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/4987069469726633897'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/08/oraclevm-re-register-host.html' title='OracleVm re-Register host'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-6731381741282774576</id><published>2011-08-19T16:15:00.000-07:00</published><updated>2011-08-19T16:19:37.167-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="aruba database"/><category scheme="http://www.blogger.com/atom/ns#" term="Server database Aruba down 20 agosto 2011"/><title type='text'>Server database Aruba down 20 agosto 2011</title><content type='html'>&lt;script type=&quot;text/javascript&quot;&gt;&lt;!--
google_ad_client = &quot;pub-3969405697138697&quot;;
/* 300x250, creato 04/03/10 */
google_ad_slot = &quot;0688371718&quot;;
google_ad_width = 300;
google_ad_height = 250;
//--&gt;
&lt;/script&gt;&lt;br /&gt;
&lt;script type=&quot;text/javascript&quot;
src=&quot;http://pagead2.googlesyndication.com/pagead/show_ads.js&quot;&gt;
&lt;/script&gt;&lt;br /&gt;
&lt;br /&gt;
I server dei database di Aruba dalle 23 del 19 agosto 2011, sono andati down, o almeno non sono raggiungibili, il problema riguarda solo i server con database, tanto è vero che i siti rispondono, ma viene visualizzato un errore di connessione.&lt;br /&gt;
&lt;br /&gt;
Rimaniamo in attesa di una comunicazione ufficiale da parte di Aruba.&lt;br /&gt;
&lt;br /&gt;
&lt;script type=&quot;text/javascript&quot;&gt;&lt;!--
google_ad_client = &quot;pub-3969405697138697&quot;;
/* 200x90, creato 21/08/08 */
google_ad_slot = &quot;5769585802&quot;;
google_ad_width = 200;
google_ad_height = 90;
//--&gt;
&lt;/script&gt;&lt;br /&gt;
&lt;script type=&quot;text/javascript&quot;
src=&quot;http://pagead2.googlesyndication.com/pagead/show_ads.js&quot;&gt;
&lt;/script&gt;</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/6731381741282774576/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/08/server-database-aruba-down-20-agosto.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/6731381741282774576'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/6731381741282774576'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/08/server-database-aruba-down-20-agosto.html' title='Server database Aruba down 20 agosto 2011'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-6653408479083691869</id><published>2011-08-11T05:25:00.000-07:00</published><updated>2011-08-11T05:25:08.758-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Vmware - HA initiated a failover action in cluster"/><title type='text'>HA initiated a failover action in cluster Vmware</title><content type='html'>Ho trovato questo messaggio “HA initiated a failover action in cluster your-cluster-name in datacenter your-datacenter-name” sul mio vCenter. Niente è cambiato, le vm non sono state riavviate l&#39;HA continua a funzionare tranquillamente, per risolvere ho usato il seguente metodo:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. Turn OFF VMware HA on Cluster Feature setting.&lt;br /&gt;
2. Enable VMware HA setting again. </content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/6653408479083691869/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/08/ha-initiated-failover-action-in-cluster.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/6653408479083691869'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/6653408479083691869'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/08/ha-initiated-failover-action-in-cluster.html' title='HA initiated a failover action in cluster Vmware'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-696676674595892651</id><published>2011-06-28T03:07:00.000-07:00</published><updated>2011-06-28T03:07:55.925-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="active directory"/><category scheme="http://www.blogger.com/atom/ns#" term="backup active directory"/><title type='text'>Active directory Backup and Restore</title><content type='html'>Active Directory Recovery&lt;br /&gt;
One of the most important step in a recovery strategy for domain controllers is to perform the proper backups while everything is working correctly. In addition to regular full backups, you should perform regular system state backups. Restoring from a system state backup, is faster than restoring from a full server backup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Be aware of the Windows editions when performing a system state backup:&lt;br /&gt;
&lt;br /&gt;
With Windows Server 2008 R2 you can use Windows Backup (GUI) to take a systemstatebackup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
With Windows Server 2008 you must use wbadmin start systemstatebackup (CMD) to take a system state backup. The backup can only be saved to a local drive (not the same drive as the system state data), not to a shared folder or a disc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There is 3 type of restoring Active Directory / AD Objects&lt;br /&gt;
&lt;br /&gt;
1. Nonauthoritative:&lt;br /&gt;
&lt;br /&gt;
A nonauthoritative restore returns the domain controller and the Active Directory database to its state at the time of backup. When the domain controller returns online, Active Directory replicates the database with other DC’s on the domain. Any changes that took place since the backup are replicated to the restored domain controller.&lt;br /&gt;
&lt;br /&gt;
Most common use of a nonauthoritative restore is to bring an entire DC back from a failure.&lt;br /&gt;
&lt;br /&gt;
2. Authoritative:&lt;br /&gt;
&lt;br /&gt;
An authoritative recovery used to restore a designated object or container of objects to its state at the time of the backup. Fx., if an administrator accidentally deletes an OU that contains a large number of users. If you restore the server from backup, the default nonauthoritative process doesn’t restore the deleted OU because the domain controller is updated to the current status of its replication partners, which means that the OU is deleted.&lt;br /&gt;
&lt;br /&gt;
When you perform an authoritative restore, you prevent specific objects from the backup from being overwritten by Active Directory replication. With the authoritative restore, the Update Sequence Number (USN) is incremented so that it is higher than the existing USN of the (deleted) object in the Active Directory replication system.&lt;br /&gt;
&lt;br /&gt;
Use an authoritative restore to restore specific objects in Active Directory.&lt;br /&gt;
&lt;br /&gt;
3. Active Directory Recycle Bin&lt;br /&gt;
&lt;br /&gt;
You can use Active Directory Recycle Bin if your AD DS run with Windows Server 2008 R2 FFL/DFL . AD Recycle Bin helps to minimize directory service downtime by enhancing your ability to preserve and restore accidentally deleted Active Directory objects without restoring Active Directory data from backups, restarting Active Directory Domain Services (AD DS), or rebooting domain controllers.&lt;br /&gt;
&lt;br /&gt;
Click Here if you want to Enable AD Recycle Bin.&lt;br /&gt;
&lt;br /&gt;
The following methods show how to perform a domain controller restore. If possible, use the first method in the table.&lt;br /&gt;
&lt;br /&gt;
Dcpromo:&lt;br /&gt;
&lt;br /&gt;
If the server boots but Active Directory is corrupt, you can use dcpromo.&lt;br /&gt;
&lt;br /&gt;
Run dcpromo to remove Active Directory from the domain controller (The server will become a member server)&lt;br /&gt;
Run dcpromo again to install Active Directory. The AD data will be copied from another DC on the network.&lt;br /&gt;
Run dcpromo /forceremoval if you are unable to remove Active Directory.&lt;br /&gt;
&lt;br /&gt;
The disadvantage of using dcpromo is that the entire Active Directory database must be replicated across the network from another domain controller. However, you can use the Install from Media option to copy the database from media to reduce network traffic.&lt;br /&gt;
&lt;br /&gt;
Restore system state:&lt;br /&gt;
&lt;br /&gt;
If the server boots but Active Directory is corrupt, you can restore the system state data from a recent backup. After the backup is restored, Active Directory replication copies only the changed data to the restored domain controller. To use this method to restore a domain controller:&lt;br /&gt;
&lt;br /&gt;
Reboot the server in Directory Services Restore Mode (DSRM). Use one of the following methods:&lt;br /&gt;
Reboot the server. Following the BIOS screen, press F8. Select Directory Services Restore Mode (DSRM) .&lt;br /&gt;
At a command prompt, type: &lt;br /&gt;
bcdedit /set safeboot disrepair &lt;br /&gt;
shutdown -t 0 -r&lt;br /&gt;
From Command Prompt (Run as Administrator) Run wbadmin start systemstaterecovery to restore the system state data.&lt;br /&gt;
Restart the server in normal mode. If you used bcdedit to start the server in DSRM, type the following at a command prompt: &lt;br /&gt;
bcdedit /deletevalue safeboot &lt;br /&gt;
shutdown -t 0 -r&lt;br /&gt;
Critical volume or full server restore:&lt;br /&gt;
&lt;br /&gt;
If you are unable to reboot the server, you will need to perform a critical volume or full server restore. This restore rebuilds the entire server, along with the Active Directory database. Use the wbadmin start recovery command to start the restore. A full server restore not only restores Active Directory, but data on all other volumes as well.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To enter DSRM, you must supply the recovery mode password. You set this password during the domain controller installation. If you need to set or change the password, use the following steps:&lt;br /&gt;
&lt;br /&gt;
Open an elevated command prompt by clicking Start, then right-clicking Command Prompt and selecting Run as administrator.&lt;br /&gt;
Type ntdsutil.&lt;br /&gt;
Type set dsrm password.&lt;br /&gt;
Type reset password on server &lt;dcname&gt;.&lt;br /&gt;
Enter the password.&lt;br /&gt;
Confirm the password.&lt;br /&gt;
Type quit, then quit again.&lt;br /&gt;
&lt;br /&gt;
fonte: http://thelaith.net/2010/09/29/active-directory-backup-and-restore/</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/696676674595892651/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/06/active-directory-backup-and-restore.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/696676674595892651'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/696676674595892651'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/06/active-directory-backup-and-restore.html' title='Active directory Backup and Restore'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-1930490489415452283</id><published>2011-06-27T09:02:00.000-07:00</published><updated>2011-06-27T09:02:41.103-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="avviare liferay"/><title type='text'>Liferay avviare</title><content type='html'>Per avviare Liferay:&lt;br /&gt;
&lt;br /&gt;
/opt/liferay/liferay-portal-6.0.6/tomcat-6.0.29/bin&lt;br /&gt;
./startup.sh</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/1930490489415452283/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/06/liferay-avviare.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/1930490489415452283'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/1930490489415452283'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/06/liferay-avviare.html' title='Liferay avviare'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-7195335323667550140</id><published>2011-06-13T00:52:00.000-07:00</published><updated>2011-06-13T00:52:48.220-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="connessioni di rete"/><title type='text'>Connettere o disconnettere unità di rete</title><content type='html'>Supponiamo che il computer che ospita la risorsa condivisa si chiami SRV01, che esso condivida una cartella DATI, alla quale ha accesso l’utente Bob, che può essere definito localmente su SRV01 oppure appartenere al dominio DOMAIN. Tutti i comandi vengono impartiti da un secondo PC connesso in rete; per semplicità assumiamo che SRV01 sia configurato per accettare le connessioni dal questa seconda macchina.&lt;br /&gt;
&lt;br /&gt;
La situazione più comune è la mappatura di una unità di rete, che possiamo effettuare con il comando:&lt;br /&gt;
net use z: \\SRV01\DATI /user:Bob password se l’utente Bob è locale a SRV01, oppure&lt;br /&gt;
net use z: \\SRV01\DATI /user:DOMAIN\Bob password se l’utente è di dominio.&lt;br /&gt;
Con lo swith /savecred, nome e password vengono salvate.&lt;br /&gt;
Se invece di indicare esplicitamente la lettera da usare per la mappatura dell’unità, vogliamo utilizzare la prima lettera disponibile sul client, il comando diventa:&lt;br /&gt;
net use * \\SRV01\......&lt;br /&gt;
&lt;br /&gt;
Nel caso non si volesse scrivere in chiaro la password su una riga di comando, basta sostituirla con un asterisco, ed il sistema ce la chiederà, oscurandola.&lt;br /&gt;
Aggiungendo al comando lo switch /persistent:yes, la connessione verrà ripristinata al riavvio.&lt;br /&gt;
Una volta terminato il lavoro, per sconnettere l’unità, possiamo impartire il comando:&lt;br /&gt;
net use z: /delete&lt;br /&gt;
&lt;br /&gt;
Se si desiderasse eliminare la richiesta di conferma (serve se il comando si inserisce in uno script), il comando diventa:&lt;br /&gt;
net use z: /delete /yes&lt;br /&gt;
per cancellare tutte le mappature:&lt;br /&gt;
net use * /delete o net use * /delete /yes&lt;br /&gt;
&lt;br /&gt;
A volte può essere necessario navigare nelle risorse di un computer remoto; se un doppio click non fosse sufficiente a visualizzare la finestra di immissione di nome e password, possiamo usare il comando per autenticarci preventivamente:&lt;br /&gt;
net use \\SRV01 /user:ecc ecc ecc&lt;br /&gt;
Quest’ultimo comando serve anche per poter stampare su una stampante di rete su un host che ha bisogno di una autenticazione preventiva. Il caso tipico è quello di chi collega il proprio PC a diverse reti con diversi domini, ad esempio il sistemista che frequenta le sedi dei propri clienti e si trovi nella necessità di stampare.&lt;br /&gt;
Utilizzare i comandi dall’interfaccia carattere è molto più veloce dell’interfaccia grafica, che spesso si “pianta” inesorabilmente quando si cerca di navigare all’interno di risorse senza la preventiva autorizzazione.&lt;br /&gt;
&lt;br /&gt;
fonte: http://www.andreabeggi.net/2007/01/29/net-use/</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/7195335323667550140/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/06/connettere-o-disconnettere-unita-di.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/7195335323667550140'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/7195335323667550140'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/06/connettere-o-disconnettere-unita-di.html' title='Connettere o disconnettere unità di rete'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-5637329543265428915</id><published>2011-05-30T09:29:00.000-07:00</published><updated>2011-05-30T09:29:26.167-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="restore"/><category scheme="http://www.blogger.com/atom/ns#" term="sqlserver"/><category scheme="http://www.blogger.com/atom/ns#" term="t-sql"/><title type='text'>T-sql restore db SqlServer</title><content type='html'>RIpristinare un db tramite t-sql&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
RESTORE FILELISTONLY&lt;br /&gt;
FROM DISK = &#39;D:\wvoce_sin2010\dbwvoce.bak&#39;&lt;br /&gt;
GO&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----Make Database to single user Mode&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ALTER DATABASE db-name&lt;br /&gt;
SET SINGLE_USER WITH&lt;br /&gt;
ROLLBACK IMMEDIATE&lt;br /&gt;
&lt;br /&gt;
----Restore Database&lt;br /&gt;
RESTORE DATABASE db-name&lt;br /&gt;
FROM DISK = &#39;D:\file.bak&#39;&lt;br /&gt;
WITH REPLACE,MOVE &#39;filem-df&#39; TO &#39;D:\file.bak&#39;,&lt;br /&gt;
MOVE &#39;file-log&#39; TO &#39;C:\file.ldf&#39;&lt;br /&gt;
&lt;br /&gt;
ALTER DATABASE pentaho SET MULTI_USER&lt;br /&gt;
GO</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/5637329543265428915/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/05/t-sql-restore-db-sqlserver.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/5637329543265428915'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/5637329543265428915'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/05/t-sql-restore-db-sqlserver.html' title='T-sql restore db SqlServer'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-7247572349754919131</id><published>2011-05-30T01:19:00.000-07:00</published><updated>2011-05-30T01:19:37.002-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="sql server"/><category scheme="http://www.blogger.com/atom/ns#" term="t-sql"/><title type='text'>T-sql dare permessi a user</title><content type='html'>Per dare i permessi ad un user esistente sul nostro motore db Sql Server, tramite t-sql questi comanda da dare:&lt;br /&gt;
&lt;br /&gt;
USE db_name;&lt;br /&gt;
CREATE USER user_name FOR LOGIN login_name;&lt;br /&gt;
EXEC sp_addrolemember &#39;db_datareader&#39;, &#39;username&#39;&lt;br /&gt;
EXEC sp_addrolemember &#39;db_datawriter&#39;, &#39;username&#39;&lt;br /&gt;
EXEC sp_addrolemember &#39;db_owner&#39;, &#39;username&#39;</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/7247572349754919131/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/05/t-sql-dare-permessi-user.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/7247572349754919131'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/7247572349754919131'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/05/t-sql-dare-permessi-user.html' title='T-sql dare permessi a user'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-4760844546850699068</id><published>2011-05-28T14:25:00.000-07:00</published><updated>2011-05-28T14:35:45.946-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="adsense"/><category scheme="http://www.blogger.com/atom/ns#" term="google"/><category scheme="http://www.blogger.com/atom/ns#" term="Wordpress"/><title type='text'>Wordpress google adsense 3 posts</title><content type='html'>Google Adsense allows 3 ad strips per page as you all know. Generally, Most of the bloggers concentrate on monetizing the single pages of their blogs and leave their homepage clean without ads. If you are one of them who like ads on the Home Page like me, this will help you do it in a better way. Most of us want to show up Google ads in the first 3 posts of the blog as they grab the attention of the readers.&lt;br /&gt;
&lt;br /&gt;
This can be done with a small piece of code, without using any kind of Plugins. So, In order to integrate ads efficiently into your WordPress theme. Open up your index.php file and look for the loop. The loop begins like this..&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
&amp;lt;?php if (have_posts()) : while (have_posts()) : the_post(); ?&amp;gt;&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
and this loop should end as&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
&amp;lt;?php endwhile; else: ?&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Sorry, nothing matches that criteria.&amp;lt;/p&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;?php endif; ?&amp;gt;&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Your Google Adsense code should be placed between the start and the end of this loop. So, just pick a position (after the title or at the end of the content,where ever you want) and place the following code..&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
&amp;lt;?php if ($wp_query-&amp;gt;current_post &amp;lt; 3) { ?&amp;gt; &lt;br /&gt;&lt;br /&gt;
&amp;lt;!– Google Adsense Code goes here –&amp;gt; &lt;br /&gt;&lt;br /&gt;
&amp;lt;?php } ?&amp;gt;&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now you have to replace the commented line ( &lt;!– Google Adsense Code goes here –&gt; ) with your adsense code, save this file and update your theme.  Now your theme should display three units of adsense code in your first 3 posts just like you always wanted.</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/4760844546850699068/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/05/wordpress-google-adsense-3-posts.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/4760844546850699068'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/4760844546850699068'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/05/wordpress-google-adsense-3-posts.html' title='Wordpress google adsense 3 posts'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-5827880326617317242</id><published>2011-05-16T02:22:00.000-07:00</published><updated>2011-05-16T02:22:17.004-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="crm"/><category scheme="http://www.blogger.com/atom/ns#" term="email router"/><title type='text'>Servizio Email Router Crm non parte</title><content type='html'>Microsoft Dynamics CRM in Microsoft Dynamics CRM 4.0: &quot;il servizio router di posta elettronica potrebbe non eseguire il thread di background principale di servizio&quot;&lt;br /&gt;
Per risolvere il problema, attenersi alla procedura descritta di seguito:&lt;br /&gt;
&lt;br /&gt;
    Eliminare il file Microsoft.Crm.Tools.EmailAgent.SystemState.xml.&lt;br /&gt;
&lt;br /&gt;
    Note&lt;br /&gt;
        Per impostazione predefinita, il file Microsoft.Crm.Tools.EmailAgent.SystemState.xml è nella seguente cartella:&lt;br /&gt;
        C:\Program Files\Microsoft CRM Email\Service&lt;br /&gt;
        Per impostazione predefinita, la cartella è una cartella nascosta. Per visualizzare questa cartella, è necessario modificare le impostazioni di Esplora risorse per visualizzare le cartelle nascoste e file nascosti.&lt;br /&gt;
    Riavviare il servizio router di posta elettronica di Microsoft Dynamics CRM.&lt;br /&gt;
&lt;br /&gt;
    Il file Microsoft.Crm.Tools.EmailAgent.SystemState.xml viene ricreato.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Se gli utenti di Microsoft Dynamics CRM sono impostati per utilizzare il router di posta elettronica e non a inoltra Mailbox, per posta elettronica in arrivo, è possibile eliminati messaggi di posta elettronica restituito a Microsoft Dynamics CRM dopo l&#39;implementazione di questa risoluzione. Se un messaggio di posta elettronica non è stato eliminato dalla cassetta postale dell&#39;utente, il router di posta elettronica Impossibile trovare il messaggio di posta elettronica dell&#39;utente nella posta in arrivo, non cercare in Microsoft Dynamics CRM e creare nuovamente il messaggio di posta elettronica in Microsoft Dynamics CRM. Per evitare questo problema, il messaggio di posta elettronica dovrà essere eliminato anche dalla cassetta postale dell&#39;utente insieme a Microsoft Dynamics CRM.&lt;br /&gt;
&lt;br /&gt;
Per evitare questa situazione, eseguire un backup dei file elencati di seguito e regolarmente memorizzarli sul desktop del server stesso.&lt;br /&gt;
&lt;br /&gt;
    Microsoft.Crm.Tools.EmailAgent.Configuration.bin&lt;br /&gt;
    Microsoft.Crm.Tools.EmailAgent.SystemState.Xml&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Se si verifica un errore gestione di configurazione router di posta elettronica di Microsoft Dynamics CRM all&#39;avvio o non è possibile avviare il servizio router di posta elettronica di Microsoft Dynamics CRM, sostituire i file sopra 2 in C:\Program Files\Microsoft CRM Email\Service. Riavviare il servizio router di posta elettronica di Microsoft Dynamics CRM e quindi avviare Microsoft Dynamics CRM E-Mail router Configuration Manager. Se il backup di questi file è più recente, sarà necessario completare la configurazione del router di posta elettronica. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
http://support.microsoft.com/kb/954522/it</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/5827880326617317242/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/05/servizio-email-router-crm-non-parte.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/5827880326617317242'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/5827880326617317242'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/05/servizio-email-router-crm-non-parte.html' title='Servizio Email Router Crm non parte'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-845678807875529422</id><published>2011-05-04T00:59:00.000-07:00</published><updated>2011-05-04T00:59:12.672-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Exchange 2010"/><category scheme="http://www.blogger.com/atom/ns#" term="W3WP High Memory Usage"/><title type='text'>Exchange 2010 W3WP High Memory Usage</title><content type='html'>Exchange 2010 High w3wp Memory Usage, it may happen that the w3wp service IIS going to saturate the Ram Exchange Server 2010 SP1.&lt;br /&gt;
This disruption can be caused by a worm &lt;b&gt;Conficker.B&lt;/b&gt;, causing delays in the delivery of mail, with frequent disconnections client.&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Stop IIs&lt;br /&gt;
&lt;br /&gt;
Downloaded from Windows Update, the update control worms in April&lt;br /&gt;
2011 and verify that there is rollup5 Microsoft Exchange 2010.</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/845678807875529422/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/05/exchange-2010-w3wp-high-memory-usage.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/845678807875529422'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/845678807875529422'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/05/exchange-2010-w3wp-high-memory-usage.html' title='Exchange 2010 W3WP High Memory Usage'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-6527233764118900224</id><published>2011-04-21T02:11:00.000-07:00</published><updated>2011-04-21T02:11:04.878-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="dhcp"/><category scheme="http://www.blogger.com/atom/ns#" term="reservation"/><title type='text'>Export e Import reservation dhcp su Win2008</title><content type='html'>Gli scope dei dhcp in windows2008 non possono essere modificati una volta creati, la subnet mask non può essere cambiata, quindi quando bisogna espandere una classe di una lan, bisogna ricreare un nuovo scope.&lt;br /&gt;
Il problema è che cancellando lo scopo esistente, vanno perse anche le reservation e le option,  quindi bisogna esportarle in questo modo:&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;netsh dhcp server &lt;serverIPAddress&gt; scope &lt;scopeAddress&gt;  dump&gt;dump.txt&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
mentre per importarle:&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;netsh exec dump.txt&lt;/b&gt;</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/6527233764118900224/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/04/export-e-import-reservation-dhcp-su.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/6527233764118900224'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/6527233764118900224'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/04/export-e-import-reservation-dhcp-su.html' title='Export e Import reservation dhcp su Win2008'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-3272192536502210563</id><published>2011-02-22T01:57:00.000-08:00</published><updated>2011-02-22T01:57:08.421-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="architettura mysql"/><category scheme="http://www.blogger.com/atom/ns#" term="database"/><category scheme="http://www.blogger.com/atom/ns#" term="mysql"/><title type='text'>Architettura database Mysql</title><content type='html'>L’articolo descrive le caratteristiche tecniche di un Database creato in ambiente MySQL, la corrispondenza tra Database e Directory sul filesystem, i tipi di tabella supportati da MySQL e l’uso della memoria.&lt;br /&gt;
&lt;br /&gt;
Caratteristiche generali&lt;br /&gt;
&lt;br /&gt;
Tutti i database creati in ambiente MySQL corrispondono fisicamente a delle sottodirectory della directory definita come datadir nel file di configurazione /etc/mysql/my.cnf&lt;br /&gt;
&lt;br /&gt;
All’interno del file my.cnf troviamo qualcosa di simile a:&lt;br /&gt;
&lt;br /&gt;
user = mysql pid-file = /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port = 3306 basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp language = /usr/share/mysql/english&lt;br /&gt;
&lt;br /&gt;
In questo caso la directory definita come datadir è la /var/lib/mysql. Questo significa che se si crea un nuovo database db_name, automaticamente verrà creata la seguente directory sul filesystem: /var/lib/mysql/db_name.&lt;br /&gt;
&lt;br /&gt;
Un database può essere vuoto, in tal caso la directory corrispondente sul filesystem sarà vuota, oppure può contenere alcune tabelle, in questo caso la directory conterrà alcuni file. Un database non può contenere un altro database. A ogni tabella del database corrisponde un file all’interno della directory corrispondente al database sul filesystem. Il file della tabella, conterrà la definizione della struttura della tabella stessa. A seconda del tipo di tabella creata, nella directory del database possiamo trovare diversi tipi di file. Per tutti i tipi di tabelle create in un database MySQL, viene generato un file che ha lo stesso nome della tabella ed estensione .frm, tale file contiene al suo interno la definizione della struttura della tabella. Quando viene creato un nuovo database in MySQL, all’interno della diretory del database viene generato il file db.opt dove vengono registrate le caratteristiche del database.&lt;br /&gt;
&lt;br /&gt;
Il contenuto del file db.opt potrebbe essere simile a:&lt;br /&gt;
&lt;br /&gt;
default-character-set=latin1 &lt;br /&gt;
default-collation=latin1_swedish_ci&lt;br /&gt;
&lt;br /&gt;
Tipi di tabelle&lt;br /&gt;
&lt;br /&gt;
MySQL supporta i seguenti tipi di tabelle:&lt;br /&gt;
&lt;br /&gt;
Tabelle tipo MyISAM&lt;br /&gt;
Tabelle tipo InnoDB&lt;br /&gt;
Tabelle tipo MERGE&lt;br /&gt;
Tabelle tipo HEAP&lt;br /&gt;
Tabelle di tipo MyISAM&lt;br /&gt;
&lt;br /&gt;
Le tabelle di tipo MyISAM hanno le seguenti caratteristiche:&lt;br /&gt;
&lt;br /&gt;
Ogni tabella è rappresentata sul disco da un file che ne descrive il formato con estensione .frm, da un file che contiene i dati con estensione .MYD e da un file contenente gli indici con estensione .MYI. Tutti i file sono memorizzati all’interno della directory del database;&lt;br /&gt;
La clausola AUTO_INCREMENT è più flessibile di tutti gli altri tipi di tabelle;&lt;br /&gt;
Possono essere utilizzate per creare tabelle di tipo MERGE;&lt;br /&gt;
Possono essere convertite in tabelle compresse, a sola lettura, molto veloci;&lt;br /&gt;
Supportano il tipo di ricerca FULLTEXT;&lt;br /&gt;
Supportano il lock a livello di tabella. In lettura l’accesso è consentito simultaneamente a più query, mentre in scrittura viene utilizzato un lock esclusivo a livello di tabella;&lt;br /&gt;
Tabelle di tipo InnoDB&lt;br /&gt;
&lt;br /&gt;
Le tabelle di tipo InnoDB hanno le seguenti caratteristiche:&lt;br /&gt;
&lt;br /&gt;
Ogni tabella è rappresentata sul disco da un file che ne descrive il formato con estensione .frm, mentre i dati e gli indici sono scritti all’interno di uno o più file utilizzati come tablespace comune a tutte le tabelle di questo tipo;&lt;br /&gt;
Questo tipo di tabella supporta le transazioni, operazioni definite all’interno degli statement BEGIN, COMMIT, ROLLBACK...&lt;br /&gt;
InnoDB fornisce un sistema per il recupero automatico dei dati in caso di crash server MySQL o del pc sul quale il server è in esecuzione;&lt;br /&gt;
InnoDB supporta le relazioni (foreign keys) e i vincoli di integrità referenziali;&lt;br /&gt;
La gestione della concorrenza per le query è gestita tramite multi- versioning e il lock a livello di riga;&lt;br /&gt;
Tabelle di tipo MERGE&lt;br /&gt;
&lt;br /&gt;
Le tabelle di tipo MERGE hanno le seguenti caratteristiche:&lt;br /&gt;
&lt;br /&gt;
Una tabella MERGE è il risultato dell’insieme di più tabelle MyISAM. Ogni tabella MERGE è rappresentata da due file, uno con estenzione .frm che contiene la definizione della struttura della tabella e uno con estensione .MRG contenente la lista dei file MyISAM che costituiscono le tabelle unite nella MERGE;&lt;br /&gt;
L’interrogazione di una tabella MERGE comporta l’interrogazione di tutte le tabelle che la compongono;&lt;br /&gt;
Una tabella MERGE può essere utile quando si ha la necessità di memorizzare grandi quantità di dati essendo un’unità logica che supera di gran lunga la capacità massima di memorizzazione dati di una tabella MyISAM;&lt;br /&gt;
Tabelle di tipo HEAP&lt;br /&gt;
&lt;br /&gt;
Le tabelle di tipo HEAP hanno le seguenti caratteristiche:&lt;br /&gt;
&lt;br /&gt;
Ogni tabella è rappresentata sul disco da un file che ne descrive il formato con estensione .frm, mentre i dati e gli indici sono scritti in memoria. Ne consegue che questo tipo di tabella è molto veloce, per contro i dati memorizzati in queste tabelle non sopravvivono al riavvio del server;&lt;br /&gt;
Le tabelle HEAP utilizzano una gran quantità di memoria, quindi non vengono usate per memorizzare grandi moli di dati;&lt;br /&gt;
MySQL e la memoria&lt;br /&gt;
&lt;br /&gt;
Il server MySQL è multithread, tecnicamente un thread è un flusso di controllo, ovvero un percorso di esecuzione attraverso il codice indipendente all’interno di un processo. Per ogni client connesso, il server di MySQL crea un thread per gestire quella connessione. Il server mantiene una cache dei gestori dei thread; quando avviene la disconnessione da parte di un client, il thread che gestiva quella connessione viene messo in cache se la cache non è piena, allo stesso modo quando un client si connette al server, gli viene assegnato un thread presente in cache. Questa gestione dei thread in cache aumenta notevolmente le prestazioni in termini di tempi di connessione e disconnessione al database.&lt;br /&gt;
&lt;br /&gt;
Il server MySQL, utilizza una serie di buffer per mantenere in memoria le informazioni necessarie a ridurre al minimo il numero degli accessi al disco. Tra i buffer utilizzati dal server di MySQL troviamo:&lt;br /&gt;
&lt;br /&gt;
le grant tables (tabelle di sistema) dove sono memorizzati i dati degli utenti del database (info, permessi, etc.). In MySQL l’accesso ai dati viene controllato per ogni query inviata dai client, bufferizzando le grant tables i tempi di risposta del server diminuiscono notevolmente;&lt;br /&gt;
il key buffer che tiene in memoria i blocchi degli indici delle tabelle;&lt;br /&gt;
la table cache che tiene in memoria i descrittori delle tabelle aperte;&lt;br /&gt;
la query cache che tiene in memoria il piano di esecuzione delle query eseguite ripetutamente;&lt;br /&gt;
la host cache che tiene in memoria la coppia nome_host / indirizzo_ip ottenuta mediante interrogazione del server DNS</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/3272192536502210563/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/02/architettura-database-mysql.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3272192536502210563'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3272192536502210563'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/02/architettura-database-mysql.html' title='Architettura database Mysql'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-3026690092715836840</id><published>2011-01-19T02:16:00.001-08:00</published><updated>2011-01-19T02:41:47.357-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cartelle condivise"/><category scheme="http://www.blogger.com/atom/ns#" term="Linux"/><category scheme="http://www.blogger.com/atom/ns#" term="samba"/><category scheme="http://www.blogger.com/atom/ns#" term="ubuntu"/><title type='text'>Montare cartella windows su Ubuntu/debian con Samba</title><content type='html'>Se non lo avete fatto in precedenza, installate il pacchetto smbfs:&lt;br /&gt;
&lt;br /&gt;
sudo apt-get install smbfs&lt;br /&gt;
&lt;br /&gt;
Create in /mnt una cartella con il nome del pc o della condivisione alla quale connettersi. Nell’esempio creeremo una cartella di nome punto_di_mount:&lt;br /&gt;
&lt;br /&gt;
sudo mkdir /mnt/punto_di_mount&lt;br /&gt;
&lt;br /&gt;
Si presume che si abbiano delle valide credenziali di accesso al sistema Windows.&lt;br /&gt;
&lt;br /&gt;
Adesso montiamo una ipotetica cartella condivisa di Windows chiamata cartella_condivisa:&lt;br /&gt;
&lt;br /&gt;
sudo mount -t smbfs -o username=username_valida //nome_pc_win/nome_condivisione /mnt/punto_di_mount&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In ambiente di rete Windows, avendo crededenziali appartenenti al gruppo Administrator, ci si può connettere direttamente alla “root” di un determinato hard disk pur non essendo formalmente stato condiviso come “cartella condivisa” semplicemente aggiungendo il simbolo $ accanto alla lettera d’unita.&lt;br /&gt;
&lt;br /&gt;
Stessa tipologia di connessione vale per il comando mount.&lt;br /&gt;
&lt;br /&gt;
Nell’esempio seguente montiamo nella solita cartella tutto il disco C del pc windows senza che sia stata ufficialmente condiviso il disco:&lt;br /&gt;
&lt;br /&gt;
sudo mount -t smbfs -o username=username_valida //nome_pc_win/c$ /mnt/punto_di_mount&lt;br /&gt;
&lt;br /&gt;
In questi casi, senza esplicita condivisione e avendo credenziali del gruppo Administrator, possiamo montare solo la “root” del disco. File e directory saranno però liberamente sfogliabili.&lt;br /&gt;
&lt;br /&gt;
Una piccola nota sui parametri del comando mount:&lt;br /&gt;
&lt;br /&gt;
Il parametro -t smbfs specifica che stiamo montando un filesystem di tipo smbfs&lt;br /&gt;
&lt;br /&gt;
Il parametro -o indica che ciò che segue è un opzione. Nel nostro caso l’opzione è il parametro username&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Montare automaticamente una cartella condivisa &lt;br /&gt;
Per fare in modo che la nostra Debian monti automaticamente all&#39;avvio la risorsa condivisa Windows, dobbiamo modificare il file /etc/fstab, il file che contiene tutte le informazioni sui filesystem montati: &lt;br /&gt;
&lt;br /&gt;
# nano /etc/fstab&lt;br /&gt;
Alla fine del file aggiungiamo la riga: &lt;br /&gt;
&lt;br /&gt;
//windowsserver/cartella /mnt/windowsserver      smbfs   username=ferdy,password=MiaPassword 0 0</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/3026690092715836840/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2011/01/montare-cartella-windows-su.html#comment-form' title='1 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3026690092715836840'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3026690092715836840'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2011/01/montare-cartella-windows-su.html' title='Montare cartella windows su Ubuntu/debian con Samba'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-5486687543058489189</id><published>2010-12-21T02:20:00.000-08:00</published><updated>2010-12-21T02:20:44.735-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="pool di nat"/><category scheme="http://www.blogger.com/atom/ns#" term="spam control rule"/><category scheme="http://www.blogger.com/atom/ns#" term="spamfilter"/><category scheme="http://www.blogger.com/atom/ns#" term="Webmin"/><title type='text'>Spam Control su Webmin permettere ip a mandare mail</title><content type='html'>Per consentire un ip ad usare il nostro SMTP, bisogna aggiungere l&#39;ip del pool di nat allo spam control rule su Webmin:&lt;br /&gt;
&lt;br /&gt;
description:       nome da assegnare&lt;br /&gt;
mail source:       network    +    IP&lt;br /&gt;
match against:     Connection information&lt;br /&gt;
Action:            Allow relayng</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/5486687543058489189/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2010/12/spam-control-su-webmin-permettere-ip.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/5486687543058489189'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/5486687543058489189'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2010/12/spam-control-su-webmin-permettere-ip.html' title='Spam Control su Webmin permettere ip a mandare mail'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-8439689431519396775</id><published>2010-12-10T15:26:00.000-08:00</published><updated>2010-12-10T15:26:25.781-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="apache2"/><category scheme="http://www.blogger.com/atom/ns#" term="virtualhost"/><title type='text'>Installare Apache2 su Debian Lenny</title><content type='html'>n questo articolo effettueremo un’installazione passo-passo del web server apache2, integreremo il php come modulo ed infine installeremo proftpd per poter aggiornare il nostro sito via ftp.&lt;br /&gt;
&lt;br /&gt;
-Installazione di apache2 e php&lt;br /&gt;
&lt;br /&gt;
Ecco i primi comandi da eseguire&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;apt-get update&lt;/blockquote&gt;&lt;br /&gt;
&lt;blockquote&gt;apt-get install apache2-mpm-prefork libapache2-mod-php5 php-pear php5-imagick php5-curl php5-gd php5-imap php5-mcrypt php5-mysql php5-xmlrpc php5-xsl&lt;/blockquote&gt;&lt;br /&gt;
Eseguendo “ps ax” vedrete gia’ apache in esecuzione:&lt;br /&gt;
&lt;br /&gt;
6163 ? Ss 0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9227 ? S 0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9228 ? S 0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9229 ? S 0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9230 ? S 0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9231 ? S 0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
&lt;br /&gt;
La configurazione di default crea un sito con la document root in&lt;br /&gt;
&lt;br /&gt;
/var/www/&lt;br /&gt;
&lt;br /&gt;
inserire in /etc/apache2/apache2.conf questo prima della riga “# Include the virtual host configurations:” (verso la fine del file)&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;AddType application/x-httpd-php .php&lt;/blockquote&gt;&lt;br /&gt;
e riavviate il servizio&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;/etc/init.d/apache2 restart&lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Se dopo il riavvio appare questo messaggio di errore:&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;&lt;i&gt;* Restarting web server apache2 apache2: Could not reliably determine the server&#39;s fully qualified domain name, using 127.0.1.1 for ServerName&lt;br /&gt;
... waiting apache2: Could not reliably determine the server&#39;s fully qualified domain name, using 127.0.1.1 for ServerName&lt;/i&gt;&lt;/blockquote&gt;&lt;br /&gt;
To fix that problem, you need to edit the httpd.conf file. Open the terminal and type,&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;sudo gedit /etc/apache2/httpd.conf&lt;/blockquote&gt;By default httpd.conf file will be blank. Now, simply add the following line to the file.&lt;br /&gt;
&lt;br /&gt;
ServerName localhost&lt;br /&gt;
Save the file and exit from gEdit.&lt;br /&gt;
&lt;br /&gt;
Finally restart the server.&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;sudo /etc/init.d/apache2 restart&lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Se dobbiamo ospitare un solo dominio, allora il lavoro e’ quasi terminato.&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Pubblicando questo file&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;/var/www/info.php&lt;/blockquote&gt;&lt;br /&gt;
con questo contenuto&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;&lt;?php

// Show all information, defaults to INFO_ALL
phpinfo();

// Show just the module information.
// phpinfo(8) yields identical results.
phpinfo(INFO_MODULES);

?&gt;&lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
Avremo modo (accedendo con un browser web all’indirizzo www.tuosito.it/info.php) di visualizzare la configurazione del php installato.&lt;br /&gt;
Tutte le modifiche al php dovranno essere effettuate al file /etc/php5/apache2/php.ini e dovrete riavviare il server web (/etc/init.d/apache2 restart)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Virtualhost (più siti sullo stesso host)&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Se invece desiderate ospitare piu’ di un sito allora dovrete create dei virtual host. Si possono creare di due tipi, ip based (quando ad ogni sito e’ riservato un proprio indirizzo ip) oppure name based (se sullo stesso indirizzo ip sono ospitati piu’ siti). In questo articolo vediamo come installare sullo stesso indirizzo ip piu’ di un sito. Cancelliamo la configurazione del sito di default:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;rm -f /etc/apache2/sites-available/*&lt;br /&gt;
rm -f /etc/apache2/sites-enabled/*&lt;/blockquote&gt;&lt;br /&gt;
creiamo le cartelle che dovranno contenere i dati del sito sito (dati web e file di log)&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;mkdir -p /var/www/virtual_hosts/www.tuosito.it/htdocs&lt;br /&gt;
mkdir -p /var/www/virtual_hosts/www.tuosito.it/logs&lt;/blockquote&gt;&lt;br /&gt;
Generiamo un file index con un messaggio di benvenuto&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;echo “Il mio primo sito” &gt; /var/www/virtual_hosts/www.tuosito.it/htdocs/index.html&lt;/blockquote&gt;&lt;br /&gt;
accediamo nella cartella /etc/apache2/sites-available/ (qui sono contenuti i siti ospitati, anche quelli non abilitati)&lt;br /&gt;
&lt;br /&gt;
cd /etc/apache2/sites-available/&lt;br /&gt;
&lt;br /&gt;
creiamo il file associato al sito. chiamiamolo per esempio www.tuosito.it e scriviamo questo al suo interno:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;&lt;VirtualHost *:80&gt;&lt;br /&gt;
ServerName www.tuosito.it&lt;br /&gt;
ServerAdmin luca@tuosito.it&lt;br /&gt;
&lt;br /&gt;
DocumentRoot /var/www/virtual_hosts/www.tuosito.it/htdocs&lt;br /&gt;
&lt;br /&gt;
ErrorLog /var/www/virtual_hosts/www.tuosito.it/logs/error.log&lt;br /&gt;
&lt;br /&gt;
LogLevel crit&lt;br /&gt;
&lt;br /&gt;
CustomLog /var/www/virtual_hosts/www.tuosito.it/logs/access.log combined&lt;br /&gt;
ServerSignature On&lt;br /&gt;
&lt;/VirtualHost&gt;&lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
N.B. cambiare il nome del virtualhost e correggere il percorso di riferitmento dei log e della document root adattandola al vostro sito.&lt;br /&gt;
&lt;br /&gt;
Adesso abilitiamolo. I siti abilitati sono quelli presenti nella cartella /etc/apache2/sites-enabled/. Dato che abbiamo gia’ creato la nostra configurazione, per abilitare il sito bastera’ creare un link simbolito da sites-enabled verso sites-available. Si fa in questo modo:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;cd /etc/apache2/sites-enabled/&lt;br /&gt;
ln -s ../sites-available/www.tuosito.it&lt;/blockquote&gt;&lt;br /&gt;
Riavviare apache&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;/etc/init.d/apache2 restart&lt;/blockquote&gt;</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/8439689431519396775/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2010/12/installare-apache2-su-debian-lenny.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/8439689431519396775'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/8439689431519396775'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2010/12/installare-apache2-su-debian-lenny.html' title='Installare Apache2 su Debian Lenny'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-7226623351781800285</id><published>2010-12-10T01:45:00.000-08:00</published><updated>2010-12-10T01:45:15.659-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="plesk"/><category scheme="http://www.blogger.com/atom/ns#" term="qmail"/><category scheme="http://www.blogger.com/atom/ns#" term="smtp"/><title type='text'>Although I&#39;m listed as a best-preference MX or a for that host</title><content type='html'>Another one that I don&#39;t have to fix often so I&#39;ll likely forget it.&lt;br /&gt;
&lt;br /&gt;
Qmail error &quot;Although I&#39;m listed as a best-preference MX or a for that host, it isn&#39;t in my controls/locals file, so I don&#39;t treat it as local. (#5.4.6)&quot;&lt;br /&gt;
&lt;br /&gt;
It shows up in the log concatenated:&lt;br /&gt;
&lt;br /&gt;
failure: Sorry._Although_I&#39;m_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn&#39;t_in_my_cont&lt;br /&gt;
rol/locals_file,_so_I_don&#39;t_treat_it_as_local._(#5.4.6)/&lt;br /&gt;
&lt;br /&gt;
Anyway, I fixed it, hopefully correctly, by placing the hostname in the /var/qmail/control/locals file and the /var/qmail/control/rcpthosts file and restarting qmail.&lt;br /&gt;
&lt;br /&gt;
Restart qmail /etc/init.d/qmail restart</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/7226623351781800285/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2010/12/although-im-listed-as-best-preference.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/7226623351781800285'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/7226623351781800285'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2010/12/although-im-listed-as-best-preference.html' title='Although I&#39;m listed as a best-preference MX or a for that host'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-3704363254669710119</id><published>2010-11-18T07:31:00.000-08:00</published><updated>2010-11-18T07:31:43.708-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Debian"/><category scheme="http://www.blogger.com/atom/ns#" term="Hardened PHP"/><category scheme="http://www.blogger.com/atom/ns#" term="php5"/><category scheme="http://www.blogger.com/atom/ns#" term="sicurezza"/><category scheme="http://www.blogger.com/atom/ns#" term="suhonin"/><title type='text'>Install Suhosin debian Lenny</title><content type='html'>I am quite surprised about it but not many people know Suhosin extension, particularly shared webhosts and even administrators of dedicated web servers. Suhosin is a well-known PHP extension made by Stefan Esser, PHP security researcher.&lt;br /&gt;
&lt;br /&gt;
With any PHP software, you cannot protect yourself from unexperienced programmers, creating errors in applications that lead to most obvious security issues (unsecure include() on user input, unprotected mail forms, etc.).&lt;br /&gt;
&lt;br /&gt;
We have been running Suhosin on all our servers with a great success and so far we didn&#39;t find any problems with Drupal and any other PHP software.&lt;br /&gt;
&lt;br /&gt;
How does Suhosin work and what does it protects against? You can either install it as a PHP module or as a PHP patch and recompile yourself. The huge advantage of a standard module is that you don&#39;t have to recompile PHP itself and you might not loose any possible vendor support. With the patch, you get a bit more protection but you need to recompile PHP everytime there is a new PHP version (And without proper server administration, I bet you will forget and make things even worse).&lt;br /&gt;
&lt;br /&gt;
Therefore I usually recommend installing Suhosin module as it&#39;s also in standard Debian/Ubuntu:&lt;br /&gt;
&lt;br /&gt;
sudo apt-get install php5-suhosin&lt;br /&gt;
For Red Hat/CentOS, there are quite a few howtos on installing Suhosin (second option).&lt;br /&gt;
&lt;br /&gt;
What does Suhosin protect against?&lt;br /&gt;
&lt;br /&gt;
■The only stable and real PHP remote file include protection available - including php://input, etc. (very important)&lt;br /&gt;
■Protects against HTTP Response Splitting Vulnerabilities&lt;br /&gt;
■Protects against scripts manipulating the memory_limit&lt;br /&gt;
■Adds protection against newline attacks to mail() (very important)&lt;br /&gt;
■Filters ASCIIZ characters from user input&lt;br /&gt;
■Ignores GET, POST, COOKIE variables with the following names: GLOBALS, _COOKIE, _ENV, _FILES, _GET, _POST, _REQUEST, _SERVER, _SESSION, HTTP_COOKIE_VARS, HTTP_ENV_VARS, HTTP_GET_VARS, HTTP_POST_VARS, HTTP_POST_FILES, HTTP_RAW_POST_DATA, HTTP_SERVER_VARS, HTTP_SESSION_VARS&lt;br /&gt;
■Supports verification of uploaded files through an external script (want automatic antivirus checking of EVERY uploaded file? Done!)&lt;br /&gt;
■Allows disabling the preg_replace() /e modifier&lt;br /&gt;
■Allows disabling eval() and blacklist/whitelist of eval functions!&lt;br /&gt;
■And more and lot more and a lot much more.&lt;br /&gt;
Did I tell you that I consider shared webhosts running PHP without Suhosin as irresponsible?&lt;br /&gt;
&lt;br /&gt;
Configuration&lt;br /&gt;
What about configuring Suhosin? The configuration file is either in /etc/php5/conf.d/suhosin.ini or integrated in php.ini, based on your Linux distribution. This is a config we use, together with explanation:&lt;br /&gt;
&lt;br /&gt;
# Enable Suhosin.&lt;br /&gt;
extension=suhosin.so&lt;br /&gt;
&lt;br /&gt;
# How many directory traversals are permitted? &quot;../dir&quot; is OK,&lt;br /&gt;
# &quot;../../../../../dir&quot; is not (5 times &gt; 4).&lt;br /&gt;
suhosin.executor.include.max_traversal=4&lt;br /&gt;
&lt;br /&gt;
# Disable /e in preg_replace which is usually used insecurely. Feel free to&lt;br /&gt;
# turn on at dedicated servers and slap everybody who uses /e.&lt;br /&gt;
suhosin.executor.disable_emodifier=Off&lt;br /&gt;
&lt;br /&gt;
# Protect mail forms against spammer attacks (Effectively disables any headers&lt;br /&gt;
# injected from user input. Very important.&lt;br /&gt;
suhosin.mail.protect=2&lt;br /&gt;
&lt;br /&gt;
# Upper limit for memory. When safe_mode is disabled, users can use ini_set to&lt;br /&gt;
# change their memory limit, with Suhosin up to this amount.&lt;br /&gt;
suhosin.memory_limit=256M&lt;br /&gt;
&lt;br /&gt;
# What to do when Suhosin filters out something. 402 = 402 HTTP response.&lt;br /&gt;
# See Suhosin conf.&lt;br /&gt;
suhosin.filter.action=402&lt;br /&gt;
&lt;br /&gt;
# Maximum limits for variables coming from COOKIE, POST and GET.&lt;br /&gt;
# These are reasonable values (based on experience).&lt;br /&gt;
suhosin.request.max_array_depth=4096&lt;br /&gt;
suhosin.request.max_array_index_length=2048&lt;br /&gt;
suhosin.request.max_name_length=2048&lt;br /&gt;
suhosin.request.max_value_length=650000&lt;br /&gt;
suhosin.request.max_vars=4096&lt;br /&gt;
suhosin.post.max_array_depth=8048&lt;br /&gt;
suhosin.post.max_array_index_length=1024&lt;br /&gt;
suhosin.post.max_name_length=2048&lt;br /&gt;
suhosin.post.max_totalname_length=8048&lt;br /&gt;
suhosin.post.max_vars=4096&lt;br /&gt;
&lt;br /&gt;
# Maximum file uploads in a script.&lt;br /&gt;
suhosin.upload.max_uploads=100&lt;br /&gt;
&lt;br /&gt;
# Newest thing we learned. Disable any include,curl,fpassthru,base64_encode,mail&lt;br /&gt;
# and others in eval(). This is Security by obscurity, however it works&lt;br /&gt;
# very well for shared hosts when an attacker is able to upload a bad&lt;br /&gt;
# script. Most of the current scripts use obfuscated code decoded from&lt;br /&gt;
# base64 and then eval()&#39;ed. This stops them, until they learn something new.&lt;br /&gt;
suhosin.executor.eval.blacklist=include,include_once,require,require_once,&lt;br /&gt;
curl_init,fpassthru,file,base64_encode,base64_decode,mail,exec,system,proc_open,&lt;br /&gt;
leak,syslog,pfsockopen,shell_exec,ini_restore,symlink,stream_socket_server,&lt;br /&gt;
proc_nice,popen,proc_get_status,dl, pcntl_exec, pcntl_fork, pcntl_signal,&lt;br /&gt;
pcntl_waitpid, pcntl_wexitstatus, pcntl_wifexited, pcntl_wifsignaled,&lt;br /&gt;
pcntl_wifstopped, pcntl_wstopsig, pcntl_wtermsig, socket_accept,&lt;br /&gt;
socket_bind, socket_connect, socket_create, socket_create_listen,&lt;br /&gt;
socket_create_pair,link,register_shutdown_function,register_tick_function&lt;br /&gt;
&lt;br /&gt;
# Feel free to turn on, disables eval() at all.&lt;br /&gt;
suhosin.executor.disable_eval=Off&lt;br /&gt;
&lt;br /&gt;
# We don&#39;t use but feel free. Function whitelist!&lt;br /&gt;
# Anything that&#39;s not in this list will not be permitted!&lt;br /&gt;
suhosin.executor.func.whitelist=&lt;br /&gt;
&lt;br /&gt;
# This is equivalent to disable_functions in php.ini.&lt;br /&gt;
suhosin.executor.func.blacklist=&lt;br /&gt;
&lt;br /&gt;
# Log all actions into Syslog.&lt;br /&gt;
suhosin.log.syslog = S_ALL &amp; ~S_SQL&lt;br /&gt;
&lt;br /&gt;
# Check all file uploads using some script.&lt;br /&gt;
# The script must write &quot;1&quot; as a first line of standard output&lt;br /&gt;
# to allow the upload, anything else to disallow.&lt;br /&gt;
suhosin.upload.verification_script=/opt/check.sh&lt;br /&gt;
Based on my experience, Suhosin works very well, even together with PHP Xcache and Memcache.&lt;br /&gt;
&lt;br /&gt;
See Hardened PHP for more configuration directives.</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/3704363254669710119/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2010/11/install-suhosin-debian-lenny.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3704363254669710119'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3704363254669710119'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2010/11/install-suhosin-debian-lenny.html' title='Install Suhosin debian Lenny'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-3442866857163739333</id><published>2010-11-16T03:36:00.000-08:00</published><updated>2010-11-16T03:36:13.332-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Debian"/><category scheme="http://www.blogger.com/atom/ns#" term="ftp"/><category scheme="http://www.blogger.com/atom/ns#" term="VSFTPD"/><title type='text'>Configurazione VSFTP</title><content type='html'>Configurazione VsFtp&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
nano /etc/vsftpd.conf &lt;br /&gt;
&lt;br /&gt;
configurazione base del vsftpd.conf:&lt;br /&gt;
&lt;br /&gt;
----------------------------&lt;br /&gt;
anonymous_enable=NO&lt;br /&gt;
anon_upload_enable=NO&lt;br /&gt;
anon_mkdir_write_enable=NO&lt;br /&gt;
local_enable=YES&lt;br /&gt;
write_enable=YES&lt;br /&gt;
local_umask=022&lt;br /&gt;
dirmessage_enable=YES&lt;br /&gt;
xferlog_enable=YES&lt;br /&gt;
xferlog_file=/var/log/vsftpd.log&lt;br /&gt;
xferlog_std_format=YES&lt;br /&gt;
ascii_upload_enable=YES&lt;br /&gt;
ascii_download_enable=YES&lt;br /&gt;
ls_recurse_enable=NO&lt;br /&gt;
listen_port=21&lt;br /&gt;
connect_from_port_20=NO&lt;br /&gt;
listen=YES&lt;br /&gt;
background=YES&lt;br /&gt;
# definiamo una chroot() jail&lt;br /&gt;
chroot_local_user=YES&lt;br /&gt;
check_shell=NO&lt;br /&gt;
userlist_deny=NO&lt;br /&gt;
# definiamo una lista di utenti autorizzati&lt;br /&gt;
# nel file /etc/vsftpd.user_list&lt;br /&gt;
userlist_enable=YES&lt;br /&gt;
userlist_file=/etc/vsftpd.user_list &lt;br /&gt;
------------------------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
CREAZIONE DEGLI UTENTI&lt;br /&gt;
&lt;br /&gt;
Ripeto, visto che è fondamentale: ogni utente del server FTP è anche un utente del sistema linux!&lt;br /&gt;
&lt;br /&gt;
Aggiungiamo adesso il primo utente linux (pippo), e creiamo cartella relativa sulla cartella ftp.&lt;br /&gt;
&lt;br /&gt;
mkdir /var/ftp/pippo&lt;br /&gt;
useradd -d /var/ftp/pippo pippo&lt;br /&gt;
chown /var/ftp/pippo pippo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
nano /etc/vsftpd.user_list &lt;br /&gt;
&lt;br /&gt;
# file /etc/vsftpd.user_list&lt;br /&gt;
# Lista Utenti Autorizzati&lt;br /&gt;
pippo&lt;br /&gt;
pluto&lt;br /&gt;
topolino &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Una volta configurato il server FTP, e testato in tutte le funzionalità, sarebbe bello e professionale aggiungere un messaggio iniziale di benvenuto.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Questo messaggio sarà contenuto in un semplice file di testo (/etc/welcome.banner).&lt;br /&gt;
&lt;br /&gt;
Aggiungere al file /etc/vsftpd.conf le seguenti righe:&lt;br /&gt;
&lt;br /&gt;
# Aggiunge un messaggio iniziale&lt;br /&gt;
banner_file=/etc/welcome.banner&lt;br /&gt;
&lt;br /&gt;
Poi creare il file di puro testo (/etc/welcome.banner)&lt;br /&gt;
&lt;br /&gt;
Benvenuti sul server FTP di Mario Rossi.&lt;br /&gt;
Inserisci i tuoi dati per l’autenticazione&lt;br /&gt;
Tutte le attivita sono monitorate.&lt;br /&gt;
Ti auguriamo un buon lavoro….&lt;br /&gt;
&lt;br /&gt;
(o qualsiasi altra cosa vi venga in mente!)&lt;br /&gt;
&lt;br /&gt;
e far ripartire il server:&lt;br /&gt;
/etc/init.d/vsftpd restart</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/3442866857163739333/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2010/11/configurazione-vsftp.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3442866857163739333'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/3442866857163739333'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2010/11/configurazione-vsftp.html' title='Configurazione VSFTP'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-8157681262391451016</id><published>2010-11-15T09:31:00.000-08:00</published><updated>2010-11-15T09:31:11.575-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="esecuzione"/><category scheme="http://www.blogger.com/atom/ns#" term="fedora"/><category scheme="http://www.blogger.com/atom/ns#" term="file bin"/><title type='text'>Installazione file BIN in Fedora</title><content type='html'>1&lt;br /&gt;
Open a Terminal by clicking &quot;Applications,&quot; &quot;System Tools&quot; and &quot;Terminal.&quot;&lt;br /&gt;
2&lt;br /&gt;
Navigate to the directory containing the .bin file in the Terminal with the &quot;cd&quot; command. For example, open the Downloads folder by typing &quot;cd Downloads&quot; into the Terminal and pressing &quot;Enter.&quot;&lt;br /&gt;
3&lt;br /&gt;
Make the .bin file executable by typing &quot;chmod +x&quot; into the Terminal, pressing &quot;Space,&quot; typing the name of the file and pressing &quot;Enter.&quot; For example, make &quot;File.bin&quot; executable by typing &quot;chmod +x File.bin&quot; into the Terminal and pressing &quot;Enter.&quot;&lt;br /&gt;
4&lt;br /&gt;
Become root by typing &quot;su&quot; into the Terminal, pressing &quot;Enter,&quot; typing your root password when prompted and pressing &quot;Enter.&quot; Installing a .bin file system-wide requires root access; some .bin file may install for a single user if you are not root.&lt;br /&gt;
5&lt;br /&gt;
Run the .bin file by typing &quot;./&quot; followed by the .bin file&#39;s name into the Terminal window and pressing &quot;Enter.&quot; For example, run &quot;File.bin&quot; by typing &quot;./File.bin&quot; and pressing &quot;Enter.&quot; The &quot;./&quot; at the start of the command tells the Terminal to look for the specified file in the current directory, and not in system directories containing Linux commands.&lt;br /&gt;
6&lt;br /&gt;
Complete the .bin file&#39;s installer by following the instructions on your screen. As with Windows software installers, each .bin file has its own interface.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Read more: How to Install a Bin File in Fedora | eHow.com http://www.ehow.com/how_6860652_install-bin-file-fedora.html#ixzz15NAiCojI</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/8157681262391451016/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2010/11/installazione-file-bin-in-fedora.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/8157681262391451016'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/8157681262391451016'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2010/11/installazione-file-bin-in-fedora.html' title='Installazione file BIN in Fedora'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7937478262084849847.post-4595828675589413238</id><published>2010-11-05T09:00:00.000-07:00</published><updated>2010-11-17T03:34:12.911-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="apache2"/><category scheme="http://www.blogger.com/atom/ns#" term="Debian"/><category scheme="http://www.blogger.com/atom/ns#" term="php5"/><category scheme="http://www.blogger.com/atom/ns#" term="proftpd"/><title type='text'>Installazione Apache2 Php5 Proftpd su Debian Lenny</title><content type='html'>In questo articolo effettueremo un’installazione passo-passo del web server apache2, integreremo il php come modulo ed infine installeremo proftpd per poter aggiornare il nostro sito via ftp.&lt;br /&gt;
&lt;br /&gt;
-Installazione di apache2 e php&lt;br /&gt;
&lt;br /&gt;
Ecco i primi comandi da eseguire&lt;br /&gt;
&lt;br /&gt;
apt-get update&lt;br /&gt;
&lt;br /&gt;
apt-get install apache2-mpm-prefork libapache2-mod-php5 php-pear php5-imagick php5-curl php5-gd php5-imap php5-mcrypt php5-mysql php5-xmlrpc php5-xsl&lt;br /&gt;
&lt;br /&gt;
Eseguendo “ps ax” vedrete gia’ apache in esecuzione:&lt;br /&gt;
&lt;br /&gt;
6163 ?        Ss     0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9227 ?        S      0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9228 ?        S      0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9229 ?        S      0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9230 ?        S      0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
9231 ?        S      0:00 /usr/sbin/apache2 -k start&lt;br /&gt;
&lt;br /&gt;
La configurazione di default crea un sito con la document root in&lt;br /&gt;
&lt;br /&gt;
/var/www/&lt;br /&gt;
&lt;br /&gt;
inserire in /etc/apache2/apache2.conf questo prima della riga “# Include the virtual host configurations:” (verso la fine del file)&lt;br /&gt;
&lt;br /&gt;
AddType application/x-httpd-php .php&lt;br /&gt;
&lt;br /&gt;
e riavviate il servizio&lt;br /&gt;
&lt;br /&gt;
/etc/init.d/apache2 restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
aslam@aslam:~$ sudo /etc/init.d/apache2 restart&lt;br /&gt;
* Restarting web server apache2                                                apache2: Could not reliably determine the server&#39;s fully qualified domain name, using 127.0.1.1 for ServerName&lt;br /&gt;
... waiting apache2: Could not reliably determine the server&#39;s fully qualified domain name, using 127.0.1.1 for ServerName&lt;br /&gt;
&lt;br /&gt;
To fix that problem, you need to edit the httpd.conf file. Open the terminal and type,&lt;br /&gt;
&lt;br /&gt;
sudo gedit /etc/apache2/httpd.conf&lt;br /&gt;
By default httpd.conf file will be blank. Now, simply add the following line to the file.&lt;br /&gt;
&lt;br /&gt;
ServerName localhost&lt;br /&gt;
Save the file and exit from gEdit.&lt;br /&gt;
&lt;br /&gt;
Finally restart the server.&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/apache2 restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------------------------&lt;br /&gt;
&lt;br /&gt;
Se dobbiamo ospitare un solo dominio, allora il lavoro e’ quasi terminato.&lt;br /&gt;
&lt;br /&gt;
Pubblicando questo file&lt;br /&gt;
&lt;br /&gt;
/var/www/info.php&lt;br /&gt;
&lt;br /&gt;
con questo contenuto&lt;br /&gt;
&lt;br /&gt;
&lt;?php
phpinfo();
?&gt;&lt;br /&gt;
&lt;br /&gt;
Avremo modo (accedendo con un browser web all’indirizzo www.tuosito.it/info.php) di visualizzare la configurazione del php installato.&lt;br /&gt;
Tutte le modifiche al php dovranno essere effettuate al file /etc/php5/apache2/php.ini e dovrete riavviare il server web (/etc/init.d/apache2 restart)&lt;br /&gt;
Potrete passare tranquillamente alla sezione relativa all’installazione di proftpd se questa configurazione e’ adatta all’utilizzo che intendete fare del server web. Se invece desiderate ospitare piu’ di un sito allora dovrete create dei virtual host. Si possono creare di due tipi, ip based (quando ad ogni sito e’ riservato un proprio indirizzo ip) oppure name based (se sullo stesso indirizzo ip sono ospitati piu’ siti). In questo articolo vediamo come installare sullo stesso indirizzo ip piu’ di un sito. Cancelliamo la configurazione del sito di default&lt;br /&gt;
&lt;br /&gt;
rm -f /etc/apache2/sites-available/*&lt;br /&gt;
rm -f /etc/apache2/sites-enabled/*&lt;br /&gt;
&lt;br /&gt;
creiamo le cartelle che dovranno contenere i dati del sito sito (dati web e file di log)&lt;br /&gt;
&lt;br /&gt;
mkdir -p /var/www/virtual_hosts/www.tuosito.it/htdocs&lt;br /&gt;
mkdir -p /var/www/virtual_hosts/www.tuosito.it/logs&lt;br /&gt;
&lt;br /&gt;
Generiamo un file index con un messaggio di benvenuto&lt;br /&gt;
&lt;br /&gt;
echo “Il mio primo sito” &gt; /var/www/virtual_hosts/www.tuosito.it/htdocs/index.html&lt;br /&gt;
&lt;br /&gt;
accediamo nella cartella /etc/apache2/sites-available/ (qui sono contenuti i siti ospitati, anche quelli non abilitati)&lt;br /&gt;
&lt;br /&gt;
cd /etc/apache2/sites-available/&lt;br /&gt;
&lt;br /&gt;
creiamo il file associato al sito. chiamiamolo per esempio www.tuosito.it e scriviamo questo al suo interno&lt;br /&gt;
&lt;br /&gt;
&lt;virtualhost *:80&gt;&lt;br /&gt;
ServerName www.tuosito.it&lt;br /&gt;
ServerAdmin luca@tuosito.it&lt;br /&gt;
&lt;br /&gt;
DocumentRoot /var/www/virtual_hosts/www.tuosito.it/htdocs&lt;br /&gt;
&lt;br /&gt;
ErrorLog /var/www/virtual_hosts/www.tuosito.it/logs/error.log&lt;br /&gt;
&lt;br /&gt;
LogLevel crit&lt;br /&gt;
&lt;br /&gt;
CustomLog /var/www/virtual_hosts/www.tuosito.it/logs/access.log combined&lt;br /&gt;
ServerSignature On&lt;br /&gt;
&lt;/VirtualHost&gt;&lt;br /&gt;
&lt;br /&gt;
N.B. cambiare il nome del virtualhost e correggere il percorso di riferitmento dei log e della document root adattandola al vostro sito.&lt;br /&gt;
&lt;br /&gt;
Adesso abilitiamolo. I siti abilitati sono quelli presenti nella cartella /etc/apache2/sites-enabled/. Dato che abbiamo gia’ creato la nostra configurazione, per abilitare il sito bastera’ creare un link simbolito da sites-enabled  verso sites-available. Si fa in questo modo:&lt;br /&gt;
&lt;br /&gt;
cd /etc/apache2/sites-enabled/&lt;br /&gt;
ln -s ../sites-available/www.tuosito.it&lt;br /&gt;
&lt;br /&gt;
Riavviare apache&lt;br /&gt;
&lt;br /&gt;
/etc/init.d/apache2 restart&lt;br /&gt;
&lt;br /&gt;
- Procediamo con l’installazione di proftpd&lt;br /&gt;
&lt;br /&gt;
Anche in questo caso utilizzaremo apt per installare il daemon&lt;br /&gt;
&lt;br /&gt;
apt-get install proftpd&lt;br /&gt;
&lt;br /&gt;
Nel menu’ “ProFTPD configuration” scegliamo l’opzione “standalone”&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Creiamo l’utente del sito&lt;br /&gt;
&lt;br /&gt;
adduser sito1&lt;br /&gt;
&lt;br /&gt;
Eseguiamo l’applicazione&lt;br /&gt;
&lt;br /&gt;
vipw&lt;br /&gt;
&lt;br /&gt;
Cambiamo la home dell’utente facendola puntare alla cartella htdocs del sito (quindi da /home/sito1 a /var/www/virtual_hosts/www.tuosito.it/htdocs/) e disabilitiamo l’accesso via ssh impostando la shell da /bin/bash a /bin/false&lt;br /&gt;
&lt;br /&gt;
Usciamo da vipw (digitando :wq) ed impostiamo /bin/false come shell valida per l’accesso ftp.&lt;br /&gt;
Si fa inserendo la riga /bin/false in /etc/shells&lt;br /&gt;
&lt;br /&gt;
echo “/bin/false” &gt;&gt; /etc/shells&lt;br /&gt;
&lt;br /&gt;
Impostiamo il corretto proprietario ai dati&lt;br /&gt;
&lt;br /&gt;
cd /var/www/virtual_hosts/www.tuosito.it/&lt;br /&gt;
chown sito1:sito1 htdocs -R&lt;br /&gt;
&lt;br /&gt;
Finito! Adesso il nostro sito e’ aggiornabile via ftp.&lt;br /&gt;
Ecco la registrazione di una sessione di prova effettuata:&lt;br /&gt;
&lt;br /&gt;
ftp www.tuosito.it&lt;br /&gt;
Connected to www.tuosito.it&lt;br /&gt;
&lt;br /&gt;
220 ProFTPD 1.3.1 Server (Debian) [::ffff:XXX.251.36.131]&lt;br /&gt;
Name (www.tuosito.it): sito1&lt;br /&gt;
331 Password required for sito1&lt;br /&gt;
Password:&lt;br /&gt;
230 User sito1 logged in&lt;br /&gt;
Remote system type is UNIX.&lt;br /&gt;
Using binary mode to transfer files.&lt;br /&gt;
ftp&gt; ls&lt;br /&gt;
227 Entering Passive Mode (XXX,251,36,131,10,87).&lt;br /&gt;
150 Opening ASCII mode data connection for file list&lt;br /&gt;
-rw-r–r–   1 sito1    sito1          18 Sep 25 10:27 index.html&lt;br /&gt;
-rw-r–r–   1 sito1    sito1          20 Sep 25 12:46 info.php&lt;br /&gt;
226 Transfer complete&lt;br /&gt;
ftp&gt; put dummy.file.gz&lt;br /&gt;
local: dummy.file.gz remote: dummy.file.gz&lt;br /&gt;
227 Entering Passive Mode (XXX,251,36,131,18,30).&lt;br /&gt;
150 Opening BINARY mode data connection for dummy.file.gz&lt;br /&gt;
226 Transfer complete&lt;br /&gt;
1038 bytes sent in 0.00 secs (3607.4 kB/s)&lt;br /&gt;
ftp&gt; ls&lt;br /&gt;
227 Entering Passive Mode (XXX,251,36,131,13,95).&lt;br /&gt;
150 Opening ASCII mode data connection for file list&lt;br /&gt;
-rw-r–r–   1 sito1    sito1        1038 Sep 25 17:50 dummy.file.gz&lt;br /&gt;
-rw-r–r–   1 sito1    sito1          18 Sep 25 10:27 index.html&lt;br /&gt;
-rw-r–r–   1 sito1    sito1          20 Sep 25 12:46 info.php&lt;br /&gt;
226 Transfer complete&lt;br /&gt;
ftp&gt; dele dummy.file.gz&lt;br /&gt;
250 DELE command successful&lt;br /&gt;
ftp&gt; ls&lt;br /&gt;
227 Entering Passive Mode (XXX,251,36,131,16,89).&lt;br /&gt;
150 Opening ASCII mode data connection for file list&lt;br /&gt;
-rw-r–r–   1 sito1    sito1          18 Sep 25 10:27 index.html&lt;br /&gt;
-rw-r–r–   1 sito1    sito1          20 Sep 25 12:46 info.php&lt;br /&gt;
226 Transfer complete&lt;br /&gt;
ftp&gt; quit&lt;br /&gt;
221 Goodbye.</content><link rel='replies' type='application/atom+xml' href='http://adminskill.blogspot.com/feeds/4595828675589413238/comments/default' title='Commenti sul post'/><link rel='replies' type='text/html' href='http://adminskill.blogspot.com/2010/11/installazione-apache2-php5-proftpd-su.html#comment-form' title='0 Commenti'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/4595828675589413238'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7937478262084849847/posts/default/4595828675589413238'/><link rel='alternate' type='text/html' href='http://adminskill.blogspot.com/2010/11/installazione-apache2-php5-proftpd-su.html' title='Installazione Apache2 Php5 Proftpd su Debian Lenny'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>