The easy way to deploy .NET framework 3.5sp1

I had a task to deploy the framework .Net 3.5sp1 over than 1000 PC, the Microsoft way

To resolve this was by GPO, or when you try it you will find many and

Many problem s and difficulties.

I had to try something else, what i needed was a silent or automatic way of deployment.

After a long time spend in searching about free software to make a new

Package (msi or exe), I found Auto it.

With it, it's so easy to understand its language of scripting even it had a tool to record

Actions and transform them to script.

This is my script of Auto it, my package is supposed to be under K: and it was a French package

#################################################################################
Run("K:\dotnetfx35.exe")
winwaitactive("Installation de Microsoft .NET Framework 3.5","J'ai lu le contrat de licence et j'A&CCEPTE ses termes et conditions")
send("{TAB}")
sleep(50)
send("{TAB}")
sleep(50)
send("{TAB}")
sleep(50)
send("{TAB}")
sleep(50)
send("{TAB}")
sleep(50)
send("{TAB}")
sleep(50)
Send("{space}")
Send("!l")
winwaitactive("Installation de Microsoft .NET Framework 3.5","Installation terminée")
send("{ENTER}")
###################################################################################

The next step was to transform it on something.exe which was so easy with "Aut2exe.exe"

Another tool of the suite Auto it.

Then we put the script.exe with the package dotnetfx35.exe under a network share.

All you have to do then is to make script batch to start the script.exe at startup.

I had some problems when I try to execute the script.exe from an UNC PATH, that's why the best way is to
Map the network share as a local resource then you start the script.exe, as you can see
In the script batch below which i put in the GPO of startup.



##########################################################

@echo off

if exist %windir%\Microsoft.NET\Framework\v3.5 goto exit

net use K: "\\network share"

start /wait K:\frame.exe

net use k: /del

exit

###########################################################

I recommend that you use it under script of shutdown GPO


because it makes some time to finish.

                                                                                       Mounir Ben Mohamed
                                                                                                  20/08/2011

Bacula client & iptables

Bacula client a besoin d'autorisations afin de contacter le serveur de sauvegarde Bacula, en résumé ces 2 lignes sont suffisantes:

iptables -A INPUT -p tcp --dport 9102 -j ACCEPT

iptables -A OUTPUT -p tcp --dport 9103 -j ACCEPT

Don't forget, you can check this problem by telnet IP_adress 9102 !

NTPDATE PROBLEMS

Lors de l'intégration d'un poste debian dans un environnement Active Directory Windows 2003/2008, l'une des étapes nécessaires est la synchronisation du temps avec le controleur du domaine.



Premier problème: la version du ntpdate 4.2.6p2 est bugé & la version 4.2.6p3
de ntpdate n'est pas disponible via apt-get install.



Solution: installation de la nouvelle version depuis les sources.

Etapes:

1/apt-get install gcc make  (nous avons besoin d'installer un compilateur)

2/téléchargez la version stable:
wget http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/ntp-4.2.6p3.tar.gz


3/tar xvf ntp-4.2.6p3.tar.gz

4/cd ntp-4.2.6p3

5/  ./configure

6/make

7/make install


Alors, il vous reste plus que faire la synchronisation
manuellement:

/usr/local/bin/ntpdate IP_DU_SERVEUR_NTP

Ou à travers un cron.




Deuxième problème: le message d'erreur de ntpdate

ntpdate[13944]: the NTP socket is in use, exiting


Solution:

c'est un conflit entre ntpdate & ntpd. Il faut choisir entre l'un deux
pour faire la synchronisation.