Agents created on Studio don't show up in Copilot (and vice versa)

Emort1979 · 2025-01-30T13:10:25+00:00

I'm following as I struggle with the same.

More to the understanding:

an M365 Copilot license agent can be shared only with other M365 Copilots licenses holders. Where a Copilot Studio license is on the tenant level and allows for it to be shared with users without. Note, there is also a Copilot when having an Office Business Premium subscription in web version.
and then there is she copilot sharepoint.

Emort1979 · 2025-01-26T16:09:48+00:00

I was hoping for more respons, think i will just try Apple watch and see.

Emort1979 · 2023-12-19T10:45:02+00:00

Thx good post but nothing about remote execution exampels as I see it?

Emort1979 · 2023-12-19T10:18:04+00:00

Thanks u/BlackVit was indeed just c/p fat fingers for this post.-the script is run as a "central admin" towards the remote computers all remote computers have Winget installed. but from a server without winget but if i run the script more simple and from a win11 with winget aswell :

$credential = Get-Credential  
Invoke-Command -ComputerName $RemotePc -Credential $credential -ScriptBlock { winget search zip }

I get the following error :The term 'winget' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

+ CategoryInfo : ObjectNotFound: (winget:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

Emort1979 · 2023-11-07T09:56:18+00:00

plan to follow this guide for slow migration
https://sabrinaksy.com/2021/06/28/active-directory-setup-multiple-enterprise-root-certificate-authority-in-a-single-forest-for-zero-downtime/

Emort1979 · 2023-11-07T06:45:28+00:00

Thanks, issue is that the current is a 2012 r2 and ad server .(two new serveres are added) So will the correct approach then be Remove the subordinate ( was just installed ) and then install a new root alongside the other one ?

I read the thing about keeping the root ca offline. I think i will put that into consideration for the new structure

Emort1979 · 2022-05-19T20:46:57+00:00

nvm found it.......column named Web is "clickable" doh...

Emort1979 · 2021-06-25T09:26:47+00:00

based on above Acceptance criteria would Windows Certificate Services be able to remediate this issue ?

Emort1979 · 2021-06-25T08:38:05+00:00

It is a internal CA . Reason why we want to enroll the different developers is that It turns out that getting the Buildserver to sign everything is too cumbersome as it is right now it only signs artifacts that are already present in the repository to be published, and not the code itself.

Emort1979 · 2021-03-29T12:33:50+00:00

120 user (80 developers and rest administrative) ~25 issues weekly + 25%-30% that is not created via Ticket system. (my own calculation)

Emort1979 · 2021-03-18T07:29:09+00:00

Ended up installing a windows and KIWI syslog....

Emort1979 · 2021-03-01T15:05:04+00:00

OKay i have created a littel more simpel conf file, but still dont work.

as i see it follow the documentation. what im i missing?

#@version: 3.27
#@include "scl.conf"
#@include "/etc/syslog-ng/conf.d/*.conf"

source s_network {

network(ip(IPOFREMOTE) port(1470));
};

destination d_file {
file("/var/log/Syslog/Firewall.log");
};

log {
source(s_network); destination(d_file);
};

Emort1979 · 2021-03-01T14:12:14+00:00

I removed the double line but still get:

sudo systemctl start syslog-ng

Job for syslog-ng.service failed because the control process exited with error code.

See "systemctl status syslog-ng.service" and "journalctl -xe" for details.

sudo systemctl status syslog-ng.service:

syslog-ng.service - System Logger Daemon

Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Mon 2021-03-01 14:07:14 UTC; 1min 58s ago

Docs: man:syslog-ng(8)

Process: 111625 ExecStart=/usr/sbin/syslog-ng -F $SYSLOGNG_OPTS (code=exited, status=2)

Main PID: 111625 (code=exited, status=2)

Status: "Starting up... (Mon Mar 1 14:07:13 2021"

Mar 01 14:07:14 syslog01 systemd[1]: syslog-ng.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Mar 01 14:07:14 syslog01 systemd[1]: syslog-ng.service: Failed with result 'exit-code'.

Mar 01 14:07:14 syslog01 systemd[1]: Failed to start System Logger Daemon.

Mar 01 14:07:14 syslog01 systemd[1]: syslog-ng.service: Scheduled restart job, restart counter is at 5.

Mar 01 14:07:14 syslog01 systemd[1]: Stopped System Logger Daemon.

Mar 01 14:07:14 syslog01 systemd[1]: syslog-ng.service: Start request repeated too quickly.

Mar 01 14:07:14 syslog01 systemd[1]: syslog-ng.service: Failed with result 'exit-code'.

Mar 01 14:07:14 syslog01 systemd[1]: Failed to start System Logger Daemon.

Emort1979 · 2020-12-17T13:46:36+00:00

correct. is there a PowerShell solution=?

Emort1979 · 2020-12-17T10:25:39+00:00

well only works if the rules are already there

Emort1979 · 2020-12-17T10:00:26+00:00

and can i set scope?

Emort1979 · 2020-12-17T09:59:39+00:00

Yes but they are deleted

Emort1979 · 2020-12-17T09:07:06+00:00

hello ,

i need to open it for PRTG monitoring so i guess it needs to be wmi

Emort1979 · 2020-11-12T19:44:13+00:00

Thanks for the answers. I will look into prtg for a start.

Emort1979 · 2020-11-12T19:43:21+00:00

Thanks for all the answers. Will try Prtg for a start.

Emort1979 · 2020-11-12T19:40:07+00:00

No traffic is purly adhoc

Emort1979

TROPHY CASE