u/bishoptf

I have had some issues with an avaya call manager that was providing dhcp for a voice vlan and trying to get pfsense to take over for the dhcp but there needs to be additional options set for the clients, called option 242, MCIPADD=x.x.x.x,MCPORT=1719,HTTPSRVR=x.x.x.x for whatever I am not sure if the option should be a string or text, phones are not picking up the option but look to be requesting addresses, running an older version 2.7.x but does anyone know what the correct way to do this option for an avaya phone?

Thanks

Follow up post to my earlier post I was having an issue with phones not registering with the IP 500 v2, it was providing DHCP services but for whatever reason the phones were not getting addresses. I disabled dhcp on the IP 500 unit and enabled dhcp on my vlan interface for the router, now the phones are registering but none of them have dial tone. Not sure I understand how dial tone is provided, I know if I called from external it rolls over to voicemail so trunks are working but nothing internally. I still think there is something going on either with the switch port or the IP 500 data port. I need to span a port and do a network capture and see what is going on.

We have 2 combo cards d6/phone2/vcm10 combo cards and all 9608 or 9611 phones. Anyone has any suggestions on what could be causing the dial tone issue would be appreciated, thanks.

Never have had this happen and not sure where to start, have an IP office system running for some time with 96xx phones and this morning we had a power glitch, and maybe half the phones did not come back online, they come up to the extension and then discover screen. Nothing has changed, media security is disabled we do not have passwords set, IP office is reachable...I have option 242 set for dhcp telling the phone which vlan to come up on...but not sure what happened or why about half the phones had this happened. I am thinking about resetting a phone and see if it will re-register with a clean slate but not sure what else to try and thought I would ask what else to try before having to drive in and putz around with it, thanks.

Update: Again I wasn't prepared and didn't have all of my tools to truly debug what was going on but finally figured out that the Avaya IP 500 unit which was configured to be the DHCP server was not handing out addresses. At some point I may circle back and get a wireshark session to see what is actually going on but the phones were not getting addresses, tried rebooting etc. I finally just disabled dhcp on the avaya unit and enabled dhcp on my router and phones starting registering again. If anyone has any insight as to why dhcp would stop working on the unit let me know it had been that way from day one and never an issue.

Update: phones are now registering but now I am not getting dial tone on any phone...looks like this is a hardware failure or could there be any other issue?

I have an open case for a windows agent job, I have a paid subscription that includes my window agent jobs and have one job that the name vs the disk has gotten messed up, in other words the computer name does not match the disk etc. Not sure how this happened if it was due to duplicate sid or we changed the name etc but I just would like to get the disk and computer name to match. Tried to remove re-add and made things worse, started getting an invoker error so opened a ticket on Jul 29. Appears when the user returned today (laptop user) the backups are now working but still have the issue with the mismatch names. Not sure it really should take this long to resolve the issue one way or another but still waiting for support to provide guidance on how to resolve.

Can anyone tell me when it registers the pc name where does it derive the name from for the windows agent. Since this is controlled by the client side it is retrieving the name from something else since it registered to a new B&R instance, anyone know for the name and disk where does it get the names from?

Working on another case and had previously collected logs and they wanted another set and I have since upgraded to 13.1. I was collecting them from the windows console and received this warning:

"Logs export completed with warning: Failed to collect nginx logs: ensure that veeam-usr-transportsvc user has read and execute permissions for /var/log/nginx directory and all of its contents"

Logged onto the linux machine and sure enough owner and group are set to root:

"drwx--x--x. 2 root root 8192 Aug 7 00:00 nginx"

compared to something like this:

"drwxrws---. 68 root veeam-grp-log 8192 Aug 7 09:28 VeeamBackup"

Not sure what the correct permissions should be but will pass along the warning with my case notes...not sure if something did not get updated correctly during the upgrade.

I have been updating all of our local documentation for a small non-profit and currently I am the only admin so I have wanted to make sure that if I get hit by a beer truck etc, that whoever picks this up has access to all things admin. I have ensured this for all the accounts and just moved to the software appliance and forgot that they have MFA enabled but tied to an app on my phone which will do the new person no good. We use a password manager but since the software appliance only supports MFA via authenticator I believe my only option is to create a break-glass admin account without MFA if that is possible. Need to read through and see if I can turn on/off MFA for individual account vs globally. I would like to leave it enabled for the normal admin and not crazy about have an account with just the password but since passkeys or hardware tokens are not supported then not sure what to do...

How are you handling this?

In the process of trying to document the environment for a small non-profit that I have been supporting for a long time. My time is winding down but I thought I had most things covered, password manager with mulitple MFA options including a hardware yubikey to allow access to vault. But I never thought about doing the same for other sites like M365 or Duo Security etc. I have enabled MFA with the microsoft authenticator but if I was to be hit by a beer truck etc before being able to move accounts over etc, I do not think they would be able to logon etc.

I assume m365 allows for hardware tokens in ADDITION to soft tokens and if so I can register the yubikey hardware token and do the same hopefully for Duo. But it had me thinking for small shops how are folks handling secondary MFA authentication methods so a new admin is able to carry on etc...I prefer not to use email as secondary but thought I would ask to see what other options are out there, thanks.

I have supported part time a small non-profit company and while I know how important documentation is there just always was something else pressing that was more important. Well I am getting to the point where in the future I am probably going to be moving on and have started to work on trying at least for me document what they have at a high level. I assume and I know what happens when you do that but they have enough technical stuff that if the person actually knows what they are doing then they should be able based on a overview of the systems function dig into it and figure things out. I am not doing anything esoteric but I also have been doing this kind of stuff for *cough* many years. While small they have a lot of technology, just migrated the virtual environment to proxmox, they have AD environment with ADFS connected to m365, etc...

I just captured the inventory for everything they have and was about to start writing up a word document that gives a high level for each server etc, layout of the network, vlans etc. I then started to think that maybe I should do something like a wiki or use something else. Although at a high level kind of leaning towards not having it online since it would pretty much give you a working layout of their environment and if compromised would be pretty nice to have.

Just thought I would ask what are folks using for documentation, thanks.

Can you backup the Veeam Software appliance itself? I have migrated everything to the new hardened appliance but was unsure about if you could back it up and if needed application aware processing etc, thanks.

I have someone looking but trying to gather more information in regards to which majors hire out of school and/or have apprenticeship programs.

Fedex (apprenticeship)

United (no experience)

American (no experience)

Frontier (no experience)

Southwest (Internal apprenticeship)

Delta (ASM apprenticeship)

Alaska (no experience)

Is there any other majors that hire or have an apprenticeship programs? Just to be clear I am referring to apprenticeship programs like Fedex that hire WITH an A&P to gain experience etc. I am not sure about Southwest but thought I saw a posting talking about an apprenticeship program. I know it also depends on supply and demand with the airlines but wanted to try to make a list.

Thanks

Small business and recently have migrated from VMware to Proxmox and along with that migrated Veeam instance (v12) to the v13 software appliance and built out a Veeam hardened repo. Also currently use Veeam windows agent to back up the PC's and laptops. With the migration to the software appliance you basically have to re-create your jobs and has me thinking that I probably do not have things structured or optimized and thought I would get some suggestions.

Here is the current layout. Have one linux nas that is a backup target, the nas also has removable drives one for user devices and one for the servers. Users devices during the day backup to the nas user directory repo (veeam agent) and at night all of the servers backup to the nas server directories. The servers since they are online 24/7 also backup to the server removable drive (rotated offsite weekly). The user directories are rsync'd from the nas user repo (directory) to the removable drive nightly. The removable drives are only mounted over night and are not mounted during the day, still some risk with having them mounted for about 9 hours but I figure better than 24/7 and ransomware etc. with the drives rotated weekly offsite.

New to the mix is I stood up one of the old servers that we were using for the proxmox migration and re-purposed it as a Veeam hardened repo and trying to figure out how to adjust/re-do my backup strategy. Currently we try to keep three weeks worth of backups and it's mainly for deleted files or DR and needing to rebuild something due to some major issue. I created a backup copy job for the users data to go to the Hardened Repo but it then required GFS settings and made me start thinking does the HR need to have three weeks or does it need to just be latest copies etc. Also had me thinking that maybe instead of doing the rsync of the user Veeam backups to the removable drive that that I use a backup copy for that. Will also need to create a backup copy job for the servers OR I just create another backup job for the servers to go to the HR.

Sorry for the rambling post, just trying to take the time now and re-structure stuff that makes the most sense and not be overly complex. I need to better understand GFS options and ensure my backup strategy makes sense.

Probably a dumb question but I honestly cannot remember the last time I needed to replace a cmos battery and I have a Dell poweredge r330 that I have a low battery warning so I need to replace. The question is will it reset all of my bios settings when I replace or are the settings written somewhere. I am re-imaging the server so not that critical but thought I would ask and maybe save me some time.

Hate to keep posting dumb questions but my lord is the Veeam website a hot mess at trying to find stuff. I am wanting to create a Veeam Hardened Repo and there are several guides talking about how to do it with Ubuntu but I also read that Veeam had an ISO ready to go, according to them is can be found here - Customer Portal or trial downloads on Veeam’s web site. In there, click Additional Downloads > Extensions and Other > Veeam Hardened Repository ISO

I have Additional Downloads but I do not have Extensions and Other....so where can I find the ISO?

I still need to read through the windows documentation but not sure what I am going to do in order to support a couple older win10 32bit window machines that are still getting security updates but have not been upgraded for various reasons. Just did a major migration from VMware to Proxmox and with that also migrated from Veeam windows v12 installation to a v13 software appliance infrastructure which required all jobs to be rebuilt. Thought I was pretty much done but now I need to figure out how I am going to support these 2 machines since when I tried to upgrade the agent software I get this message:

"Veeam agent Your operating system is not supported by Veeam Agent for Microsoft Windows, See documentation for more details"

If I try to connect the existing agent to a v13 repo I get an error when it tries to get a license from the repo, transport timeout etc. I understand the need to move on with older window versions but really disappointed in the lack of continued support since I am not sure how I am going to backup these machines. Anyone have any suggestions, is there a workaround to get Veeam to continue to back these machines up and go to the repo or am I out of luck...

Been thinking about this and thought I would post and get other folks thoughts about Proxmox and licensing costs. I support small non-profit shops but are large enough to have a couple of servers for redundancy but do not need live migration etc. In the past before the evil Broadcom took over, VMware had very low costs for non-profits for essentials. Provided you three hosts and vCenter but no vmotion etc. Non-profit pricing from VMware was $35/yr, yeah thats not a mistake. Microsoft offers some of the same discount for their products for non-profit, steep discounts.

Takes me back to Proxmox, they have community level, basic, standard etc..but even the community level will not provide access to the Proxmox Datacenter Manager (PDM) enterprise repo which we would like to use just so we have a single pane of glass to see both nodes (no cluster) just redundant nodes with a handful of vm's running on them. We can run it without a subscription and click through the nag screens but wish there really was other options to support them. Since they made the subscription > 80% to enable the enterprise repo for PDM we would only meet that by having 2 basic subscriptions and thats not going to happen due to the cost.

I guess it's their software and they can license it how they want and I can purchase community licenses for our nodes to at least support them at some level but really wish they had more options for us small business that are running standalone nodes vs clusters etc...

Just was wondering what others think about the licensing levels etc...

I tried looking through the documentation and all I see is it talking about HotAdd for vmware, is HotAdd supported in the latest veeam software appliance and proxmox 9.x?

I am getting really close to getting everything working on a migration to the new Veeam software appliance and I have one win10 vm (still getting security updates) that is giving me a warning all the other vm's appear to be playing nice. The vm is backed up but I get a warning about not being able to index the guest system and it throws a samba error

"Failed to index guest file system. Samba failed with error: WERR_EXE_MACHINE_TYPE_MISMATCH [stderr: Query status request failed. [WERR_EXE_MACHINE_TYPE_MISMATCH]. ]"

Doing some searching says its a mismatch between using 32but vs 64bit and all the ones that are working are 64bit windows versions. I have looked through the job but I do not see anywhere I can specify that its 32bit version of windows. I am migrating to Proxmox from vmware which I have accomplished on the first host but need backups working.

Anyone have any ideas what I need to do in order to resolve?

I have been using Veeam for quite sometime but in a VMware environment and while I know I had some issues getting things working once they are working they usually continue to work. I am yet another one of those that are migrating to Proxmox from VMware for all the common reasons. I have an intermediate server running Proxmox 9 and have installed Veeam Software appliance and have what I think everything configured but I have one windows 10 vm and one windows 11 vm that I am trying to back up and each one is throwing errors. I did not add my Veeam Software appliance to the domain since its a small shop and I really prefer not to join but looks like it is sqawking about authentication issues even though I am using domain admin creds for the standard credentials for logging onto the windows vm.

Below are some of the error messages with names and ip's removed, obviously I am missing some configuration on the Veeam software appliance but not sure what, anyone have any suggestions let me know while I keep searching...thanks.

Win10 vm:

7/10/2026 10:27:32 PM Failed : Failed to prepare guest for hot backup. Error: Failed to connect to the guest OS.

[Failed to connect to guest agent. Errors: 'Samba failed with error: NT_STATUS_NO_SUCH_DOMAIN

[stderr: Kinit for xxxxx@xxx to access xxxx failed: Cannot find KDC for requested realm

Could not connect to server xxxx Connection failed: NT_STATUS_NO_SUCH_DOMAIN. ]

Samba failed with error: NT_STATUS_INVALID_PARAMETER [stderr: Could not connect to server

Connection failed: NT_STATUS_INVALID_PARAMETER. ] Samba failed with error: NT_STATUS_ACCESS_DENIED [

stderr: Kerberos auth with 'xxxx@xxx' (xxxx\yyyy) to access '1.2.3.4'

not possible Could not connect to server 1.2.3.4 Connection failed: NT_STATUS_ACCESS_DENIED. ] ']

win11 vm

7/10/2026 10:29:46 PM Failed : Failed to prepare guest for hot backup. Error: Failed to perform handshake

7/10/2026 10:29:46 PM Failed : Failed to install guest processing components for dpcgerber Error: Failed to perform handshake

UPDATE: sometimes when you read something you don't really read it, Forest for the trees, etc...so it says fore credentials to use FQDN and I just use the normal short domain\account vs domain.xyz and when I updated the credential it appears to work for the migrated vm but is failing the new vm which maybe is firewall related....thanks everyone for the suggestions....

UPDATE2: I think I have both working now without Application aware processing but I think I will need that for a couple of VM's. The new windows 11 vm was firewall related, had to allow ports 139 and 445 inbound from the veeam appliance server in order to get it working.

Update3: Backups ran, one completed fine and the one I just migrated gave another error - 7/11/2026 9:53:17 PM Failed : Failed to perform backup: Failed to prepare disks for backup (0:02:40)

Two steps forward, one step back...running proxmox 9.x and the latest veeam, not sure since this was a migrated vm from esxi what it didnt like about the disk.....