Clipchamp coming to Visual Creator in Microsoft 365 Copilot

Clipchamp will soon integrate with Visual Creator in Microsoft 365 Copilot, enabling users to effortlessly create videos by simply typing a prompt. Clipchamp will generate a custom script, find available high-quality stock footage, and assemble a video project complete with music, voiceover, text overlays, and transitions. After initial creation, t his initial draft can be further edited in the Clipchamp app and exported as an mp4 file for distribution.   As mentioned, the feature sources it images from existing stock media from Microsoft 365 service asset libraries , it does not create actual new video material.   Organizations should consider updating their training and adoption material to include the new agent and the Clipchamp tool for content creators.   This feature is mentioned in Microsoft 365 Roadmap ID 402192 , and it should be rolling out in the February-March time - frame .  

More OCS challenges

Ok, So I have the basics up and running, but is it working? Aperantly, yes.
Front end and backend now run without errormessages, and I can chat, call and use livemeeting on all the clients.

I decided not spend to much time on running around, installing applications, so I am using AD Group policies to deploy the applications. Here is a quick rundown of what I did:

Livemeeting:
  • Download software from www.livemeeting.com (Remember to download both client and outlook plugin)
  • Convert exe files to .msi files by running "LMsetup.exe -out c:\temp" (presuming c:\temp exists)
  • Create a GPO for distribution (Assign or publish, Computer or User - It depends on your preference)
  • Create Groups for filtering of the GPO
  • Add objects to the groups
  • Remove "authenticated users" from the filtering, add the desired group.
Attendant:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.

Office Communicator:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.