Re: Host showing as unsecure

[Vivek Kumar]

What OS are you using, ! I faced once with ubuntu 22  where it was showing me 
same,  it was due to the the entry in /etc/default/libvirtd file.

It should be LIBVIRTD_ARGS="—listen” rather then libvirtd_opts="-l"


Then restart the libvirtd services, 


Just verify it. 

Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 19-Dec-2023, at 9:43 PM, Brian Fossmeyer 
>  wrote:
> 
> CloudStack 4.18.1.0
> 
> 
> Thanks,
> 
> Brian
> 
> From: Wei ZHOU 
> Date: Tuesday, December 19, 2023 at 11:10 AM
> To: users@cloudstack.apache.org 
> Subject: Re: Host showing as unsecure
> Warning: This message is the first you've received from this sender 
> ustcweizhou @ gmail.com. Please click the Report Suspicious Email button if 
> you believe this email is not legitimate.
> 
> Which cloudstack version do you use ?
> 
> -Wei
> 
> On Tue, 19 Dec 2023 at 16:08, Brian Fossmeyer
> wrote:
> 
>> Thank you, I tried this several times and it has not helped. Is there
>> anything else I could try?
>> 
>> Thanks,
>> 
>> Brian
>> 
>> From: Vivek Kumar
>> Date: Tuesday, December 19, 2023 at 8:33 AM
>> To: users@cloudstack.apache.org
>> Subject: Re: Host showing as unsecure
>> Warning: This message is the first you've received from this sender
>> vivek.kumar @ indiqus.com.INVALID. Please click the Report Suspicious Email
>> button if you believe this email is not legitimate.
>> 
>> Hello Brian,
>> 
>> You can re provision the certificates,
>> 
>> Click on host and click on second options “Provision host security keys” -
>> it will re-create the certificate.
>> 
>> 
>> 
>> 
>> Vivek Kumar
>> Sr. Manager - Cloud & DevOps
>> TechOps | Indiqus Technologies
>> 
>> vivek.ku...@indiqus.com
>> www.indiqus.com
>> 
>> 
>> 
>> 
>>> On 19-Dec-2023, at 6:57 PM, Brian Fossmeyer wrote:
>>> 
>>> Hello,
>>> 
>>> Are there any specific items I could check for a host that shows
>> unsecure but connected? I have restarted the agent and management service
>> removed and rejoined, disconnected and reconnected the host and it still
>> says unsecure. It was a secure host in our previous build of the system.
>> This is the third build of our entire system and the previous two times it
>> was green and secure. I am not sure what is different this time.
>>> 
>>> Thanks,
>>> Brian
>>> 
>>> 
>>> Thanks,
>>> 
>>> Brian
>>> 
>>> Brian Fossmeyer
>>> Senior Systems Engineer, Technology
>>> 
>>> [Answers in Genesis] [Creation Museum] [Ark Encounter]
>> 
>> 
>> --
>> This message is intended only for the use of the individual or entity to
>> which it is addressed and may contain confidential and/or privileged
>> information. If you are not the intended recipient, please delete the
>> original message and any copy of it from your computer system. You are
>> hereby notified that any dissemination, distribution or copying of this
>> communication is strictly prohibited unless proper authorization has been
>> obtained for such action. If you have received this communication in error,
>> please notify the sender immediately. Although IndiQus attempts to sweep
>> e-mail and attachments for viruses, it does not guarantee that both are
>> virus-free and accepts no liability for any damage sustained as a result of
>> viruses.
>> 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Re: Host showing as unsecure

[Brian Fossmeyer]

This has been fixed on GitHub. Here are the steps that were shared with me that 
fixed the issue.

The Unsecure state in ACS indicates that the Libvirt service has been 
configured to start with TCP. For the host to be marked with the Up state, 
Libvirt must be configured to start with TLS. However, during installation of 
the ACS Agent for KVM, some sockets are automatically masked, including the TLS 
socket; making it necessary to unmask them manually. To unmask the sockets and 
reestablish communication via TLS, the following steps are needed:

  1.  Unmask sockets:

systemctl unmask libvirtd-admin.socket
systemctl unmask libvirtd-ro.socket
systemctl unmask libvirtd-tcp.socket
systemctl unmask libvirtd-tls.socket
systemctl unmask libvirtd.socket

  1.  Stop the libvirtd service:

systemctl stop libvirtd

  1.  Start libvirtd-tls.socket

systemctl start libvirtd-tls.socket

  1.  Restart the ACS agent:

systemctl restart cloudstack-agent

  1.  Enable socket libvirt-tls

systemctl enable libvirtd-tls.socket
With this, Libvirt should start with TLS and ACS will mark it with the status 
Up, instead of Unsecure.


Thanks,

Brian

From: Brian Fossmeyer 
Date: Tuesday, December 19, 2023 at 11:13 AM
To: users@cloudstack.apache.org 
Subject: Re: Host showing as unsecure
CloudStack 4.18.1.0


Thanks,

Brian

From: Wei ZHOU 
Date: Tuesday, December 19, 2023 at 11:10 AM
To: users@cloudstack.apache.org 
Subject: Re: Host showing as unsecure
Warning: This message is the first you've received from this sender ustcweizhou 
@ gmail.com. Please click the Report Suspicious Email button if you believe 
this email is not legitimate.

Which cloudstack version do you use ?

-Wei

On Tue, 19 Dec 2023 at 16:08, Brian Fossmeyer
wrote:

> Thank you, I tried this several times and it has not helped. Is there
> anything else I could try?
>
> Thanks,
>
> Brian
>
> From: Vivek Kumar
> Date: Tuesday, December 19, 2023 at 8:33 AM
> To: users@cloudstack.apache.org
> Subject: Re: Host showing as unsecure
> Warning: This message is the first you've received from this sender
> vivek.kumar @ indiqus.com.INVALID. Please click the Report Suspicious Email
> button if you believe this email is not legitimate.
>
> Hello Brian,
>
> You can re provision the certificates,
>
> Click on host and click on second options “Provision host security keys” -
> it will re-create the certificate.
>
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
>
> vivek.ku...@indiqus.com
> www.indiqus.com
>
>
>
>
> > On 19-Dec-2023, at 6:57 PM, Brian Fossmeyer wrote:
> >
> > Hello,
> >
> > Are there any specific items I could check for a host that shows
> unsecure but connected? I have restarted the agent and management service
> removed and rejoined, disconnected and reconnected the host and it still
> says unsecure. It was a secure host in our previous build of the system.
> This is the third build of our entire system and the previous two times it
> was green and secure. I am not sure what is different this time.
> >
> > Thanks,
> > Brian
> >
> >
> > Thanks,
> >
> > Brian
> >
> > Brian Fossmeyer
> > Senior Systems Engineer, Technology
> >
> > [Answers in Genesis] [Creation Museum] [Ark Encounter]
>
>
> --
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain confidential and/or privileged
> information. If you are not the intended recipient, please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result of
> viruses.
>

Re: Changeing the IP of an NFS Secondary Storage

[Antoine Boucher]

Yes - thanks again



Antoine Boucher
antoi...@haltondc.com
[o] +1-226-505-9734
www.haltondc.com

“Data security made simple”





Confidentiality Warning: This message and any attachments are intended only for 
the use of the intended recipient(s), are confidential, and may be privileged. 
If you are not the intended recipient, you are hereby notified that any review, 
retransmission, conversion to hard copy, copying, circulation or other use of 
this message and any attachments is strictly prohibited. If you are not the 
intended recipient, please notify the sender immediately by return e-mail, and 
delete this message and any attachments from your system.


> On Dec 19, 2023, at 11:20 AM, Wido den Hollander  wrote:
> 
> (Back to ML)
> 
> Op 19/12/2023 om 17:18 schreef Antoine Boucher:
>> Thank you, Wido. That's a great suggestion. Do you define all your ACS using 
>> DNS names?
> 
> Yes, I always use DNS everywhere. Never use static IPs in any of the 
> configuration.
> 
> If it's Ceph Monitors for primary storage, NFS hostnames for Primary Storage 
> or Secondary Storage.
> 
> Make sure you have a proper domain name to use for your infrastructure and 
> then just use DNS.
> 
> Wido
> 
>> I’m a fan - Regards,
>> Antoine
>> *Antoine Boucher*
>> antoi...@haltondc.com
>> [o] +1-226-505-9734
>> www.haltondc.com
>> “Data security made simple”
>> HDClogo7-small.png
>> Confidentiality Warning: This message and any attachments are intended only 
>> for the use of the intended recipient(s), are confidential, and may be 
>> privileged. If you are not the intended recipient, you are hereby notified 
>> that any review, retransmission, conversion to hard copy, copying, 
>> circulation or other use of this message and any attachments is strictly 
>> prohibited. If you are not the intended recipient, please notify the sender 
>> immediately by return e-mail, and delete this message and any attachments 
>> from your system.
>>> On Dec 19, 2023, at 10:18 AM, Wido den Hollander  wrote:
>>> 
>>> 
>>> 
>>> Op 15/12/2023 om 18:10 schreef Antoine Boucher:
 Hello, When I initially adopted ACS a few years ago, I inadvertently 
 placed my secondary storage on the storage network. Surprisingly, 
 everything functioned well in the first year.
 However, issues arose when I updated the system to the next version. The 
 SSVM failed to manage and operate the storage correctly, and I encountered 
 difficulties migrating templates and snapshots to a different SS.
 My Question:
 To permanently resolve my problem, could I change the SS IP to the 
 management network by:
  1. Modifying the address of my SS.
  2. Updating the address in the URL field of the image_store table.
  3. Deleting the existing SSVM in the zone.
  4. Reboot the Management Server (?)
>>> 
>>> I think that works. While you are at it, I suggest using a DNS name 
>>> pointing to the SS. Should you ever need to change the IP again, you can 
>>> just change the DNS without needing to touch CloudStack.
>>> 
>>> Wido
>>> 
 Any suggestions would be greatly appreciated.
 Regards,
 Antoine
 Antoine Boucher
 antoi...@haltondc.com
 [o] +1-226-505-9734
 www.haltondc.com

Re: Changeing the IP of an NFS Secondary Storage

[Wido den Hollander]

(Back to ML)

Op 19/12/2023 om 17:18 schreef Antoine Boucher:
Thank you, Wido. That's a great suggestion. Do you define all your ACS 
using DNS names?




Yes, I always use DNS everywhere. Never use static IPs in any of the 
configuration.


If it's Ceph Monitors for primary storage, NFS hostnames for Primary 
Storage or Secondary Storage.


Make sure you have a proper domain name to use for your infrastructure 
and then just use DNS.


Wido


I’m a fan - Regards,
Antoine






*Antoine Boucher*
antoi...@haltondc.com
[o] +1-226-505-9734
www.haltondc.com

“Data security made simple”


HDClogo7-small.png


Confidentiality Warning: This message and any attachments are intended 
only for the use of the intended recipient(s), are confidential, and 
may be privileged. If you are not the intended recipient, you are hereby 
notified that any review, retransmission, conversion to hard copy, 
copying, circulation or other use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient, please 
notify the sender immediately by return e-mail, and delete this message 
and any attachments from your system.




On Dec 19, 2023, at 10:18 AM, Wido den Hollander  wrote:



Op 15/12/2023 om 18:10 schreef Antoine Boucher:
Hello, When I initially adopted ACS a few years ago, I inadvertently 
placed my secondary storage on the storage network. Surprisingly, 
everything functioned well in the first year.
However, issues arose when I updated the system to the next version. 
The SSVM failed to manage and operate the storage correctly, and I 
encountered difficulties migrating templates and snapshots to a 
different SS.

My Question:
To permanently resolve my problem, could I change the SS IP to the 
management network by:

 1. Modifying the address of my SS.
 2. Updating the address in the URL field of the image_store table.
 3. Deleting the existing SSVM in the zone.
 4. Reboot the Management Server (?)


I think that works. While you are at it, I suggest using a DNS name 
pointing to the SS. Should you ever need to change the IP again, you 
can just change the DNS without needing to touch CloudStack.


Wido


Any suggestions would be greatly appreciated.
Regards,
Antoine
Antoine Boucher
antoi...@haltondc.com
[o] +1-226-505-9734
www.haltondc.com

Re: Host showing as unsecure

[Brian Fossmeyer]

CloudStack 4.18.1.0


Thanks,

Brian

From: Wei ZHOU 
Date: Tuesday, December 19, 2023 at 11:10 AM
To: users@cloudstack.apache.org 
Subject: Re: Host showing as unsecure
Warning: This message is the first you've received from this sender ustcweizhou 
@ gmail.com. Please click the Report Suspicious Email button if you believe 
this email is not legitimate.

Which cloudstack version do you use ?

-Wei

On Tue, 19 Dec 2023 at 16:08, Brian Fossmeyer
wrote:

> Thank you, I tried this several times and it has not helped. Is there
> anything else I could try?
>
> Thanks,
>
> Brian
>
> From: Vivek Kumar
> Date: Tuesday, December 19, 2023 at 8:33 AM
> To: users@cloudstack.apache.org
> Subject: Re: Host showing as unsecure
> Warning: This message is the first you've received from this sender
> vivek.kumar @ indiqus.com.INVALID. Please click the Report Suspicious Email
> button if you believe this email is not legitimate.
>
> Hello Brian,
>
> You can re provision the certificates,
>
> Click on host and click on second options “Provision host security keys” -
> it will re-create the certificate.
>
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
>
> vivek.ku...@indiqus.com
> www.indiqus.com
>
>
>
>
> > On 19-Dec-2023, at 6:57 PM, Brian Fossmeyer wrote:
> >
> > Hello,
> >
> > Are there any specific items I could check for a host that shows
> unsecure but connected? I have restarted the agent and management service
> removed and rejoined, disconnected and reconnected the host and it still
> says unsecure. It was a secure host in our previous build of the system.
> This is the third build of our entire system and the previous two times it
> was green and secure. I am not sure what is different this time.
> >
> > Thanks,
> > Brian
> >
> >
> > Thanks,
> >
> > Brian
> >
> > Brian Fossmeyer
> > Senior Systems Engineer, Technology
> >
> > [Answers in Genesis] [Creation Museum] [Ark Encounter]
>
>
> --
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain confidential and/or privileged
> information. If you are not the intended recipient, please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result of
> viruses.
>

Re: Host showing as unsecure

[Wei ZHOU]

Which cloudstack version do you use ?

-Wei

On Tue, 19 Dec 2023 at 16:08, Brian Fossmeyer
 wrote:

> Thank you, I tried this several times and it has not helped. Is there
> anything else I could try?
>
> Thanks,
>
> Brian
>
> From: Vivek Kumar 
> Date: Tuesday, December 19, 2023 at 8:33 AM
> To: users@cloudstack.apache.org 
> Subject: Re: Host showing as unsecure
> Warning: This message is the first you've received from this sender
> vivek.kumar @ indiqus.com.INVALID. Please click the Report Suspicious Email
> button if you believe this email is not legitimate.
>
> Hello Brian,
>
> You can re provision the certificates,
>
> Click on host and click on second options “Provision host security keys” -
> it will re-create the certificate.
>
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
>
> vivek.ku...@indiqus.com
> www.indiqus.com
>
>
>
>
> > On 19-Dec-2023, at 6:57 PM, Brian Fossmeyer wrote:
> >
> > Hello,
> >
> > Are there any specific items I could check for a host that shows
> unsecure but connected? I have restarted the agent and management service
> removed and rejoined, disconnected and reconnected the host and it still
> says unsecure. It was a secure host in our previous build of the system.
> This is the third build of our entire system and the previous two times it
> was green and secure. I am not sure what is different this time.
> >
> > Thanks,
> > Brian
> >
> >
> > Thanks,
> >
> > Brian
> >
> > Brian Fossmeyer
> > Senior Systems Engineer, Technology
> >
> > [Answers in Genesis] [Creation Museum] [Ark Encounter]
>
>
> --
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain confidential and/or privileged
> information. If you are not the intended recipient, please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result of
> viruses.
>

Re: Changeing the IP of an NFS Secondary Storage

[Wido den Hollander]

Op 15/12/2023 om 18:10 schreef Antoine Boucher:

Hello, When I initially adopted ACS a few years ago, I inadvertently placed my 
secondary storage on the storage network. Surprisingly, everything functioned 
well in the first year.

However, issues arose when I updated the system to the next version. The SSVM 
failed to manage and operate the storage correctly, and I encountered 
difficulties migrating templates and snapshots to a different SS.

My Question:

To permanently resolve my problem, could I change the SS IP to the management 
network by:

  1. Modifying the address of my SS.
  2. Updating the address in the URL field of the image_store table.
  3. Deleting the existing SSVM in the zone.
  4. Reboot the Management Server (?)


I think that works. While you are at it, I suggest using a DNS name 
pointing to the SS. Should you ever need to change the IP again, you can 
just change the DNS without needing to touch CloudStack.


Wido



Any suggestions would be greatly appreciated.

Regards,
Antoine


Antoine Boucher
antoi...@haltondc.com
[o] +1-226-505-9734
www.haltondc.com

Re: Changeing the IP of an NFS Secondary Storage

[Wido den Hollander]

Op 15/12/2023 om 18:10 schreef Antoine Boucher:

Hello, When I initially adopted ACS a few years ago, I inadvertently placed my 
secondary storage on the storage network. Surprisingly, everything functioned 
well in the first year.

However, issues arose when I updated the system to the next version. The SSVM 
failed to manage and operate the storage correctly, and I encountered 
difficulties migrating templates and snapshots to a different SS.

My Question:

To permanently resolve my problem, could I change the SS IP to the management 
network by:

  1. Modifying the address of my SS.
  2. Updating the address in the URL field of the image_store table.
  3. Deleting the existing SSVM in the zone.
  4. Reboot the Management Server (?)


I think that works. While you are at it, I suggest using a DNS name 
pointing to the SS. Should you ever need to change the IP again, you can 
just change the DNS without needing to touch CloudStack.


Wido



Any suggestions would be greatly appreciated.

Regards,
Antoine


Antoine Boucher
antoi...@haltondc.com
[o] +1-226-505-9734
www.haltondc.com

Re: Host showing as unsecure

[Brian Fossmeyer]

Thank you, I tried this several times and it has not helped. Is there anything 
else I could try?

Thanks,

Brian

From: Vivek Kumar 
Date: Tuesday, December 19, 2023 at 8:33 AM
To: users@cloudstack.apache.org 
Subject: Re: Host showing as unsecure
Warning: This message is the first you've received from this sender vivek.kumar 
@ indiqus.com.INVALID. Please click the Report Suspicious Email button if you 
believe this email is not legitimate.

Hello Brian,

You can re provision the certificates,

Click on host and click on second options “Provision host security keys” - it 
will re-create the certificate.




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com
www.indiqus.com




> On 19-Dec-2023, at 6:57 PM, Brian Fossmeyer wrote:
>
> Hello,
>
> Are there any specific items I could check for a host that shows unsecure but 
> connected? I have restarted the agent and management service removed and 
> rejoined, disconnected and reconnected the host and it still says unsecure. 
> It was a secure host in our previous build of the system. This is the third 
> build of our entire system and the previous two times it was green and 
> secure. I am not sure what is different this time.
>
> Thanks,
> Brian
>
>
> Thanks,
>
> Brian
>
> Brian Fossmeyer
> Senior Systems Engineer, Technology
>
> [Answers in Genesis] [Creation Museum] [Ark Encounter]


--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. If you are not the intended recipient, please delete the
original message and any copy of it from your computer system. You are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless proper authorization has been
obtained for such action. If you have received this communication in error,
please notify the sender immediately. Although IndiQus attempts to sweep
e-mail and attachments for viruses, it does not guarantee that both are
virus-free and accepts no liability for any damage sustained as a result of
viruses.

Re: Changeing the IP of a NFS Secondary Storage

[Antoine Boucher]

Can anyone provide insights into my proposed solution, helping me determine 
whether it is advisable to proceed cautiously with modifications to the 
management server database?

Regards,
Antoine


> On Dec 15, 2023, at 12:10 PM, Antoine Boucher  wrote:
> 
> Hello, When I initially adopted ACS a few years ago, I inadvertently placed 
> my secondary storage on the storage network. Surprisingly, everything 
> functioned well in the first year. 
> 
> However, issues arose when I updated the system to the next version. The SSVM 
> failed to manage and operate the storage correctly, and I encountered 
> difficulties migrating templates and snapshots to a different SS.
> 
> My Question: 
> 
> To permanently resolve my problem, could I change the SS IP to the management 
> network by: 
> 
>  1. Modifying the address of my SS. 
>  2. Updating the address in the URL field of the image_store table. 
>  3. Deleting the existing SSVM in the zone. 
>  4. Reboot the Management Server (?) 
> 
> Any suggestions would be greatly appreciated.
> 
> Regards,
> Antoine
> 
> 
> Antoine Boucher
> antoi...@haltondc.com
> [o] +1-226-505-9734
> www.haltondc.com
> 

Re: Host showing as unsecure

[Vivek Kumar]

Hello Brian,

You can re provision the certificates, 

Click on host and click on second options “Provision host security keys” - it 
will re-create the certificate.




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 19-Dec-2023, at 6:57 PM, Brian Fossmeyer 
>  wrote:
> 
> Hello,
> 
> Are there any specific items I could check for a host that shows unsecure but 
> connected? I have restarted the agent and management service removed and 
> rejoined, disconnected and reconnected the host and it still says unsecure. 
> It was a secure host in our previous build of the system. This is the third 
> build of our entire system and the previous two times it was green and 
> secure. I am not sure what is different this time.
> 
> Thanks,
> Brian
> 
> 
> Thanks,
> 
> Brian
> 
> Brian Fossmeyer
> Senior Systems Engineer, Technology
> 
> [Answers in Genesis] [Creation Museum] 
>   [Ark Encounter] 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Host showing as unsecure

[Brian Fossmeyer]

Hello,

Are there any specific items I could check for a host that shows unsecure but 
connected? I have restarted the agent and management service removed and 
rejoined, disconnected and reconnected the host and it still says unsecure. It 
was a secure host in our previous build of the system. This is the third build 
of our entire system and the previous two times it was green and secure. I am 
not sure what is different this time.

Thanks,
Brian


Thanks,

Brian

Brian Fossmeyer
Senior Systems Engineer, Technology

[Answers in Genesis] [Creation Museum] 
  [Ark Encounter]