@scottalanmiller said in Installing the agent:

@wls-itguy said in Installing the agent:

@scottalanmiller said in Installing the agent:

@wls-itguy said in Installing the agent:

@scottalanmiller said in Installing the agent:

@wls-itguy said in Installing the agent:

And on Windows 2008 R2 using the SuperDOS script:

PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.

Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.

Just now?

Yes.

That's not good. Those errors don't appear to be from the install, though, they appear to be from existing packages that can't update.

Yea, that thing is FUBAR'd! Guess I have something else to work on tomorrow

@scottalanmiller said in Installing the agent:

@wls-itguy said in Installing the agent:

@scottalanmiller said in Installing the agent:

@wls-itguy said in Installing the agent:

And on Windows 2008 R2 using the SuperDOS script:

PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.

Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.

Just now?

Yes.

@scottalanmiller said in Installing the agent:

@wls-itguy said in Installing the agent:

And on Windows 2008 R2 using the SuperDOS script:

PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.

Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.

The Windows box didn't have any updates needed.

@scottalanmiller said in Installing the agent:

@wls-itguy looks like you have a problem with your system and insserve. I've seen it recommended to remove it as too many things don't support it.

apt-get remove insserv

Not sure if I can as I might need it for the EZ Proxy part that is on that server. But I'll see what I can do.

And on Windows 2008 R2 using the SuperDOS script:

Installing on Debian 8.8

root@library:~# wget -q -O - https://gitlab.com/dutchcolonial/sodiumsuiteinstallers/raw/master/unix.sh | bash -s 79bcd200ab29ef4fac4adc5a34ff0a9b7d065146
Hit http://security.debian.org jessie/updates InRelease
Ign http://ftp.us.debian.org jessie InRelease     
Get:1 http://ftp.us.debian.org jessie-updates InRelease [145 kB]
Hit http://security.debian.org jessie/updates/main Sources 
Hit http://security.debian.org jessie/updates/main amd64 Packages       
Hit http://ftp.us.debian.org jessie Release.gpg                                
Hit http://security.debian.org jessie/updates/main Translation-en              
Hit http://ftp.us.debian.org jessie Release                             
Hit http://ftp.us.debian.org jessie-updates/main Sources                
Get:2 http://ftp.us.debian.org jessie-updates/main amd64 Packages/DiffIndex [10.9 kB]
Get:3 http://ftp.us.debian.org jessie-updates/main Translation-en/DiffIndex [3,688 B]
Hit http://ftp.us.debian.org jessie/main Sources
Hit http://ftp.us.debian.org jessie/main amd64 Packages
Hit http://ftp.us.debian.org jessie/main Translation-en
Fetched 160 kB in 2s (63.0 kB/s)        
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  dctrl-tools debconf debconf-i18n debconf-utils libpgm-5.1-0 libsodium13 libzmq3 python-jinja2 python-m2crypto python-mako
  python-markupsafe python-msgpack python-yaml python-zmq salt-common
Suggested packages:
  debtags debconf-doc libterm-readline-gnu-perl libgtk2-perl libnet-ldap-perl libqtgui4-perl libqtcore4-perl python-jinja2-doc
  python-beaker python-mako-doc salt-doc python-augeas
The following NEW packages will be installed:
  dctrl-tools debconf-utils libpgm-5.1-0 libsodium13 libzmq3 python-jinja2 python-m2crypto python-mako python-markupsafe
  python-msgpack python-psutil python-yaml python-zmq salt-common salt-minion
The following packages will be upgraded:
  debconf debconf-i18n
2 upgraded, 15 newly installed, 0 to remove and 127 not upgraded.
2 not fully installed or removed.
Need to get 0 B/3,641 kB of archives.
After this operation, 13.3 MB of additional disk space will be used.
Reading changelogs... Done
Preconfiguring packages ...
Setting up udev (215-17+deb8u7) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
insserv: warning: script 'K00ezproxy' missing LSB tags and overrides
insserv: warning: script 'ezproxy' missing LSB tags and overrides
insserv: There is a loop between service ezproxy and mountnfs if started
insserv:  loop involving service mountnfs at depth 5
insserv:  loop involving service nfs-common at depth 4
insserv: There is a loop between service rc.local and mountall if started
insserv:  loop involving service mountall at depth 6
insserv:  loop involving service checkroot-bootclean at depth 5
insserv: There is a loop between service rc.local and urandom if started
insserv:  loop involving service urandom at depth 7
insserv: There is a loop between service ezproxy and mountdevsubfs if started
insserv:  loop involving service mountdevsubfs at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service rc.local if started
insserv: There is a loop between service ezproxy and rc.local if started
insserv:  loop involving service rc.local at depth 3
insserv:  loop involving service ezproxy at depth 2
insserv:  loop involving service rsyslog at depth 1
insserv: There is a loop between service ezproxy and mountall-bootclean if started
insserv:  loop involving service mountall-bootclean at depth 1
insserv:  loop involving service kbd at depth 12
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv:  loop involving service mountnfs-bootclean at depth 12
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv:  loop involving service networking at depth 9
insserv:  loop involving service hwclock at depth 4
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools (0.120+deb8u2) ...
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
Errors were encountered while processing:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)
bash: line 29: uuidgen: command not found
Failed to restart salt-minion.service: Unit salt-minion.service failed to load: No such file or directory.
Failed to execute operation: No such file or directory```

@scottalanmiller said in Installing the agent:

For Mac the installer should work fine, I believe. It's pretty new. For scanning, we are working on getting it to keep reporting. It keeps working, but acts like it isn't. So it collects data, but says that the data is old.

Should the Mac at least check in once?

@dustinb3403 said in Installing the agent:

Do you have wget or curl installed, I believe debian comes with both. So either should work.

wget worked for Debian. Ubuntu failed but that is because of root being disabled by default.

Not a linux guy by default. Which one do I use for Debian? How about Mac?

@scottalanmiller said in DHCP ranges seperate for IP Phones and PCs?:

@wls-itguy said in DHCP ranges seperate for IP Phones and PCs?:

@scottalanmiller said in DHCP ranges seperate for IP Phones and PCs?:

@wls-itguy said in DHCP ranges seperate for IP Phones and PCs?:

@scottalanmiller said in DHCP ranges seperate for IP Phones and PCs?:

What are you using the scan to provide?

PC info and Network info. Ticketing as well. I know SodiumSuite does all that as well.

It does indeed.

As other conversations have been had with you on this it doesn't do Network switches or phones though, correct?

If not, will that be a feature that will happen?

No, does not scan devices on which it cannot be installed.

I guess with having PRTG that really wouldn't be needed.

@scottalanmiller said in DHCP ranges seperate for IP Phones and PCs?:

@wls-itguy said in DHCP ranges seperate for IP Phones and PCs?:

@scottalanmiller said in DHCP ranges seperate for IP Phones and PCs?:

What are you using the scan to provide?

PC info and Network info. Ticketing as well. I know SodiumSuite does all that as well.

It does indeed.

As other conversations have been had with you on this it doesn't do Network switches or phones though, correct?

If not, will that be a feature that will happen?

@jaredbusch said in DHCP ranges seperate for IP Phones and PCs?:

@wls-itguy are you actually trying to make a separate subnet or just organize them in a section of you existing subnet?

If I could organize them within the subnet so 172.16.1.x/16 is the range and if all phones (FreePBX system) could get 172.16.5.x and all PCs goes 172.16.1.x range that would be great. I don't think that is possible though.

@scottalanmiller said in DHCP ranges seperate for IP Phones and PCs?:

What are you using the scan to provide?

PC info and Network info. Ticketing as well. I know SodiumSuite does all that as well.

@dafyre said in DHCP ranges seperate for IP Phones and PCs?:

@wls-itguy said in DHCP ranges seperate for IP Phones and PCs?:

@dafyre said in DHCP ranges seperate for IP Phones and PCs?:

Why split your phones off into their own subnet?

That's the reason for the post. Is there a benefit?

What size is your subnet now?

/16

That is not what I scan through though

@dafyre said in DHCP ranges seperate for IP Phones and PCs?:

Why split your phones off into their own subnet?

That's the reason for the post. Is there a benefit?

@emad-r said in DHCP ranges seperate for IP Phones and PCs?:

@wls-itguy

I think what your asking for is VLANS, otherwise how will you differentiate between phone and PC. you can use MAC address IP reservation, but thats it.

I have VLANs already. 1 for Wired, 1 for Secured WiFi (Profs and Staff), and 1 for Students and Guests.

Trying to go through my inventory through and wanting to clean things up in there. Was wondering if creating two ranges for phone and PCs would be a good idea. Not sure of the benefits or bad things about it but what better place to ask

So how long before SodiumSuite can do all of what can do?

@scottalanmiller said in How many of you...:

@wls-itguy said in How many of you...:

@dbeato said in How many of you...:

@scottalanmiller said in How many of you...:

@wls-itguy said in How many of you...:

@scottalanmiller said in How many of you...:

@wls-itguy said in How many of you...:

@scottalanmiller said in How many of you...:

I got a really nice email from someone that checked in over there last week, saw the drama, and canceled his World trip.

What did I miss? I really like going to Austin though

They deactivated both @DustinB3403 and me. We don't have accounts there anymore.

is there a thread on this? I need some interesting reading.

@dbeato made one.

Yes, I made one.

Here or there? Not finding anything but I'm not really looking all that hard

There, here isn't the right place to discuss it. Especially as a major part of their complaint was people talking about them in public, elsewhere. They are really anal about being talked about in any place where they can't selectively delete the parts of the conversation that they don't like. (Which is how I got put into perma moderation in the first place - I reported a rules and ethics breach and they immediately cut off my account in retaliation.)

I, err, um, I got nothing.

@dbeato said in How many of you...:

@scottalanmiller said in How many of you...:

@wls-itguy said in How many of you...:

@scottalanmiller said in How many of you...:

@wls-itguy said in How many of you...:

@scottalanmiller said in How many of you...:

I got a really nice email from someone that checked in over there last week, saw the drama, and canceled his World trip.

What did I miss? I really like going to Austin though

They deactivated both @DustinB3403 and me. We don't have accounts there anymore.

is there a thread on this? I need some interesting reading.

@dbeato made one.

Yes, I made one.

Here or there? Not finding anything but I'm not really looking all that hard