Category: Microsoft
Category Archives: Microsoft
Windows Update Compliance Reporting FAQ
Hi, Jonas here!
Or as we say in the north of Germany: “Moin Moin!”
I wrote a frequently asked questions document about the report solution I created some years ago. Mainly because I still receive questions about the report solution and how to deal with update related errors. If you haven’t seen my ConfigMgr report solution yet, here is the link: “Mastering Configuration Manager Patch Compliance Reporting”
Hopefully the Q&A list will help others to reach 100% patch compliance.
If that’s even possible 😉
First things first
If you spend a lot of time dealing with update related issues or processes for client operating systems, have a look at “Windows Autopatch” HERE and let Microsoft deal with that.
For server operating systems, on-premises or in the cloud have a look at “Azure Update Manager” and “A Staged Patching Solution with Azure Update Manager“.
The section: “Some key facts and prerequisites” of the blog mentioned earlier covers the basics of the report solution and should answer some questions already.
Everything else is hopefully covered by the list below.
So, lets jump in…
The OSType field does not contain any data. What should I do?
This can mean two things.
No ConfigMgr client is installed. In that case other fields like client version also contain no data. Install the client or use another collection without the system in it to run the report and therefore exclude the system from the report.
The system has not send any hardware inventory data. Check the ConfigMgr client functionality.
Some fields contain a value of 999. What does that mean?
There is no data for the system found in the ConfigMgr database when a value of 999 is shown.
“Days Since Last Online” with a value of 999 typically means that the system had no contact with ConfigMgr at all. Which either means the system has no ConfigMgr client installed or the client cannot contact any ConfigMgr management point.
“Days Since Last AADSLogon” with a value of 999 means there is no data from AD System or Group Discovery in the ConfigMgr database for the system.
“Days Since Last Boot” with a value of 999 means there is no hardware inventory data from WMI class win32_operatingsystem in the ConfigMgr database for the system.
“Month Since Last Update Install” with a value of 999 means there is no hardware inventory data from WMI class win32_quickfixengineering in the ConfigMgr database for the system.
What does WSUS Scan error stand for?
Before a system is able to install updates, it needs to scan against the WSUS server to be able to report missing updates. If that scan fails, an error will be shown in the report.
In that case, other update information might be also missing and such an error should be fixed before any other update related analysis.
I found WSUS scan errors with a comment about a WSUS GPO
The ConfigMgr client tries to set a local policy to point to WSUS client to the WSUS server of the ConfigMgr infrastructure. That process fails in case a group policy tries to do the same with a different WSUS server name.
Remove the GPO for those systems to resolve the error.
I found WSUS scan errors mentioning the registry.pol file
The ConfigMgr client tries to set a local policy to point the WSUS client to the WSUS server of the ConfigMgr infrastructure. That process results in a policy entry in: “C:Windowssystem32grouppolicyMachineRegistry.pol”
If the file cannot be accessed the WSUS entry cannot be set and the process fails.
Delete the file in that case and run “gpupdate /force” as an administrator.
IMPORTANT: Local group policy settings made manually or via ConfigMgr task sequence need to be set again if the file has been deleted.
NOTE: To avoid any other policy problems (with Defender settings for example) it is best to re-install the ConfigMgr client after the file has been re-created.
I found WSUS scan errors mentioning a proxy problem, how can I fix that?
This typically happens when a system proxy is set and the WSUS agent tries to connect to the WSUS server via that proxy and fails.
You can do the following:
Open a command prompt as admin and run “netsh winhhtp show proxy”
If a proxy is present, either remove the proxy with: “netsh winhttp reset proxy”
Or, add either the WSUS server FQDN or just the domain to the bypass list.
Example: netsh winhttp set proxy proxy-server=”proxy.domain.local:8080″ bypass-list=”<local>;wsus.domain.local;*.domain.local”
Use either “wsus.domain.local” or “*.domain.local” in case your wsus is part of domain.local.
In some cases the proxy is set for the local SYSTEM account
Open: “regedit” as administrator
Open: [HKEY_USERSS-1-5-18SoftwareMicrosoftWindowsCurrentVersionInternet SettingsConnections]
Set “ProxyEnable” to “0” to disable the use of a proxy for the system account
When should I restart systems with a pending reboot?
As soon as possible. A pending reboot might be pending from another source than just software update installations like a normal application or server role installation and might prevent security update installations.
Some systems have all updates installed, but some deployments still show as non-compliant (Column: “Deployments Non Compliant”) What can I do?
This can happen if older update deployments exist and have no compliance changes over a longer period of time. Systems in that state are typically shown as “unknown” in the ConfigMgr console under “Deployments”.
Do one of the following to resolve that:
Remove older updates from an update group in case they are no longer needed
Remove the deployment completely
Delete the deployment and create a new one.
All actions will result in a re-evaluation of the deployment.
Column “Update Collections” does not show any entries.
The system is not a member of a collection with update deployments applied and is therefore not able to install updates. Make sure the system is part of an update deployment collection.
What is the difference between “Missing Updates All” and “Missing Updates Approved”?
“Missing Updates All” are ALL updates missing for a system whether deployed or not.
“Missing Updates Approved” are just the updates which are approved, deployed, or assigned (depending on the term you use) to a system and still missing. “Missing Updates Approved” should be zero at the end of your patch cycle, while “Missing Updates All” can always have a value other than zero.
Some systems are shown without any WSUS scan or install error, but have still updates missing. What can I do to fix that?
There can be multiple reasons for that.
Make sure the system is part of a collection with update deployments first
Check the update deployment start and deadline time and if the system sees (time is past start time) and is forced to install the update (time is past deadline time)
This is visible in the report: “Software Updates Compliance – Per device deployments”. Which can be opened individually or by clicking on the number in column: “Deployments Non Compliant” in any of the list views of the report solution.
The earliest deadline for a specific update and device is visible in the report: “Software Updates Compliance – Per device” or when clicked on the number of column: “Missing Updates Approved”.
Make sure the system either has no maintenance window at all or a maintenance window which fits the start and deadline time.
Make sure a maintenance window is at least 2h long to be able to install updates in it
Also, check the timeout configured for deployed updates on each update in the ConfigMgr console.
For example, if an update has a timeout of two hours configured and the maintenance window is set to two hours, installation of the update will NOT be triggered.
Check the restart notification client settings. This is especially important in server environments where a logged on user might not see a restart warning and therefore might not act on it. The restart time will be added to the overall timeout of each update and could exceed the overall allowed installation time of a maintenance window
Check the available space on drive C:. Too little space can cause all sorts of problems.
Start “cleanmgr.exe” as admin an delete unused files.
If nothing else worked: Reboot the system and trigger updates manually
If nothing else worked: Re-install the ConfigMgr client
If nothing else worked: Follow the document: “Troubleshoot issues with WSUS client agents”
Some systems are shown as uncompliant, but all updates are installed? What can I do to fix that?
This can either be a reporting delay or a problem with update compliance state messages.
If the update installation just finished, wait at least 45 to 60 minutes. This is because the default state message send interval is set to 15 minutes and the report result is typically cached for 30 minutes.
If the update installation time is in the past, this could be due to missing state messages.
In that case, run the following PowerShell line locally on the affected machines to re-send update compliance state messages
(New-Object -ComObject “Microsoft.CCM.UpdatesStore”).RefreshServerComplianceState
Installation errors indicate an issue with the CBS store. How can this be fixed?
If the CBS store is marked corrupt no security updates can be installed and the store needs to be fixed.
the following articles describe the process in more detail:
HERE and HERE
The CBS log is located under: “C:WindowsLogsCBSCBS.log”.
The large log file size sometimes causes issues when parsing the file for the correct log entry.
In addition to that, older logfiles are stored as CAB-files and can also be quite large in size.
The following script can be used to parse even very large files and related CAB-files for store corruption entries.
Get-CBSLogState.ps1
Are there any additional resources related to update compliance issues?
Yes, the following articles can help further troubleshoot update related issues:
Troubleshoot software update management
Troubleshoot software update synchronization
Troubleshoot software update scan failures
Troubleshoot software update deployments
Deprecation of Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters – Microsoft Support
What can I do to increase my update compliance percentage?
This is an non exhaustive list of actions which can help to positively impact software update compliance:
As mentioned before do not leave a system too long in a pending reboot state.
As mentioned before make sure to always have enough space left on disk C: (~2GB+ for monthly security updates, ~10GB+ for feature updates)
Start “cleanmgr.exe” as admin and delete unused files for example.
Make sure a system has enough uptime to be able to download and install security updates.
If a system has limited bandwidth available it might need to stay online/active a while longer than other systems with more bandwidth available
You also might need to consider power settings for systems running on battery
What is a realistic update compliance percentage?
While the aim is to get to 100% fully patched systems, this goal can be quite hard in some situations. Some of the reasons behind bad patch compliance come from technical issues like the ones mentioned above under: “What can I do to increase my update compliance percentage?”. But other factors include the device delivery process for example. If you put ready to go systems on a shelf for a longer period, those devices will decrease overall patch compliance percentage.
To reach a high compliance percentage, know your workforce and know your update processes.
Reduce the blind spot and make sure each actively used system does not fall out of management due to errors, misconfigurations, or simply bad monitoring. Keep those devices on the shelf in mind and exclude them from compliance reporting for the duration of inactivity.
That’s it!
I hope you enjoyed reading this blog post. Stay safe!
Jonas Ohmsen
Microsoft Tech Community – Latest Blogs –Read More
Relational Data Synchronization between environments
Relational Data Synchronization between environments
There are business and/or technical cases where relational data should be duplicated to another environment. Since the demands of those business and/or technical cases are not the same, there are multiple technical solutions to achieve the goal.
In this article, I will discuss of the various solutions according to difference business needs, with deep dive into one family of solutions – sync solutions that is based on the database engine (DB engine). The content is Azure oriented, but the same concepts are true for other clouds as well.
I would expect that anyone that needs to sync relational data between environment can find here a good guideline.
General synchronization demands
Let us start with the typical demands:
Scenario
Latency
Typical solution family
Data Warehouse
Hours to day
ETL
Data mart
Minutes to hours
DB engine Sync
High utilized DB
Seconds to minutes
DB engine Full or Sync
High availability
Seconds
DB engine Full
Disaster Recovery
Seconds to minutes
DB engine Full
Network separation
Vary
Vary
DB engine Sync is the focus if this article. See below.
Here is high level description of those solution families:
ETL (Extract,Transform,Load):
Used for populating data warehouses or data marts from production systems
Usually, the schema on the target is more reporting friendly (star schema) than the production system
The data in the target can be in delay (usually hours) compared to the source
The source and the target can be utilizing different technologies
Tools in the market: Azure Data Factory, Informatica, Ascend
DB engine full:
Built-in replica mechanism to have another copy of the full database
With or without the ability to have one or more replicas that can be utilized as a read replica
Based on high availability, log shipping, backup & restore or storage-based solutions
Used for HA/DR and or read scale operation
Minimal latency (seconds)
Same technology
Read only on the target
DB engine sync
Tools in scope: SQL Data sync, Fabric Mirroring, Replication
Those tools support partial copy of the database
See more in the next chapter
Each option has its own pros and cons and sometimes you might use more than one solution in the same project.
In the rest of this article, I will focus on the DB engine sync solutions family usage.
More information:
ETL – Extract, transform, and load
Read only Replica: Azure SQL, PostgreSQL, MySQL
DB engine Sync Solutions Family
The need:
I cannot exaggerate the importance of choosing a synchronization solution based on your specific business needs. This is the reason that multiple solutions exist – to be able to support your specific need with a good-enough solution.
A sync process is responsible for sync data between environments. To be more exact, between source and one or more targets. The different solutions might have various kinds of characteristics.
Here are typical characteristics that you might be interested in:
Various kinds of technology
Different schema
Updates on both sides (conflict might happen)
Latency between the two copies
Maintenance efforts, skills required
The level of provider/user responsibility for the sync including re-sync probability, tools and efforts
I chose three key technologies (replication, SQL data sync, Fabric Mirroring) to discuss. The discussion is based on multiple discussions with my customers.
Replication:
Very mature technology which is supported by the majority of the relational database products
Low latency – usually seconds
Multiple flavors – transactional, merge, snapshot
Different table structure in the source and target are possible with limitations but add complexity
Multiple subscribers per source are supported
Monitoring is your responsibility and in case of failure, deep knowledge is needed to avoid reinitializing
For SQL server, you have a built-in replication monitor tool. For other databases you should check.
The monitor is not doing correction actions. Failing to track the replication status might cause a non-updated target environment
Replication of the data to a database of another provider might be possible usually with limitations. You will need a third-party tool to implement such a solution. For SQL Server Heterogeneous Database Replication is deprecated.
Azure SQL database cannot be a publisher
You must have a good DBA with specific replication knowledge to maintain the system
Typical scenarios for replication:
Filtering (part of the rows and/or the columns should be replicated
Low latency needs
Cross security boundaries with SQL authentication (see in the security section)
Cross database technologies (SQL server à Oracle)
More information:
Replication: Azure SQL MI, Azure SQL DB, PostgreSQL, MySQL
SQL Data Sync for Azure:
SQL Data Sync is a service built on Azure SQL Database that lets you synchronize the data you select bi-directionally across multiple databases, both on-premises and in the cloud, but only SQL Server based.
Azure SQL Data Sync does not support Azure SQL Managed Instance or Azure Synapse Analytics at this time
Source and target should be with the exact same schema
Multiple subscribers are supported
Typical scenarios for SQL Data Sync:
Considerable number of tables to be replicated
Managed by Azure experts (limited database knowledge needed)
SaaS solution preferred
Azure SQL database source
Bi-directional synchronization
More information:
Data Sync: Overview, Best Practices
Azure SQL Data Sync | Tips and Tricks
Mirroring in Microsoft Fabric (private preview):
The target for the synced data is sorted in delta lake table format – no need for relational database
The primary business scenario is reporting on the target
The schema cannot be changed on the target
Azure Cosmos DB, Azure SQL DB and Snowflake customers will be able to use Mirroring to mirror their data in OneLake and unlock all the capabilities of Fabric Warehouse, Direct Lake Mode, Notebooks and much more.
SQL Server, Azure PostgreSQL, Azure MySQL, Mongo DB and other databases and data warehouses will be coming in CY24.
Typical scenarios for Mirroring with Microsoft Fabric:
The target is reporting only that might integrate data from multiple sources
The cost associated with maintaining another relational engine for reporting is high. This aspect is even more significant for ISVs that are managing different environments for each customer (tenant)
Azure SQL or IaaS environment
Replacing an ETL system with no code solution
Part of your OneLake data architecture
More information:
Mirroring: Announcement, Copilot, Cosmos DB
Other aspects:
For the completeness of this article, here is a brief discussion of other aspects of the solutions that you should be aware of:
Identity and Security:
In all solutions – integrate solution is the best (replication authentication and replication security , SQL Data Sync, Mirroring).
For replication, you might use SQL authentication. For Azure SQL managed instance it is necessary.
Cost:
All the solutions do not have direct cost except for the services utilized for the source and target and possible cross data centers network bandwidth utilized.
Bi-directional and conflict resolution:
The only Azure native solution support is for SQL Data Sync.
Transactional replication – bi-directional (peer to peer) is rare but has multiple options. Last write wins is the automatic way as defined here.
Note:
Peer to peer is not supported by Azure SQL database offerings
Merge replication has more options but not on Azure SQL database offerings – see here
SQL Data Sync – Hub wins or Member wins (see here)
Mirroring – one direction only , so, not applicable
Scalability and performance:
In all solutions. You can expect reasonable pressure on the source (publisher) is expected.
SQL Data Sync add triggers to the source database while replication is using log reader (less pressure).
Monitoring and sync status:
For Replication – you have replication monitor and the tablediff utility
For SQL data Sync and Fabric mirroring – Monitoring Azure SQL Data Sync using OMS Log Analytics or Azure SQL Data Sync Health Checker
Real-time vs. Batch Synchronization:
All the solutions are well suited to real-time and short transactions. However, batch will work as well with more pressure on the SQL server log.
For Data Sync, empty tables provide the best performance at initialization time. If the target table is empty, Data Sync uses bulk insert to load the data. Otherwise, Data Sync does a row-by-row comparison and insertion to check for conflicts. If performance is not a concern, however, you can set up sync between tables that already contain data.
More information:
Empty tables provide the best performance
Choosing a DB engine Sync solution
Here is a short list of criteria that might help you choose a solution:
SQL Data Sync
The best solution for Azure SQL DB
Portal/script managed
Target should be from the SQL server family
Replication
The only solution for Azure SQL Managed Instance
Customable (filtering, schema change)
Deep database knowledge required
Fabric mirroring
Your solution where the destination can be/preferred on delta lake table format
Support multi sources (Azure SQL, Cosmos, Snowflake, more to come)
Portal/script managed
More information:
Compare SQL Data Sync with Transactional Replication
Conclusion
In the realm of data management, the need to synchronize relational data across environments arises from diverse business and technical requirements. This article has delved into the various solutions available, with a particular focus on database engine-based synchronization in the Azure ecosystem.
From the high-level demands of scenarios such as Data Warehouse, Data mart, High Utilized DB, High Availability, Disaster Recovery, to the intricacies of choosing between ETL, DB engine full, and DB engine sync solutions, we’ve explored the landscape of options available.
In the family of DB engine sync solutions, we’ve highlighted the importance of aligning your choice with specific business needs. Replication, a mature technology, offers low latency and supports various scenarios, though it requires vigilant monitoring. SQL Data Sync provides bi-directional synchronization for a considerable number of tables, managed by Azure professionals, while Microsoft Fabric’s Mirroring offers a unique approach for reporting scenarios.
Considerations such as identity and security, cost implications, conflict resolution, scalability, and monitoring have been discussed to provide a holistic view. Whether you prioritize low latency, transactional consistency, or ease of management, choosing the right solution is paramount.
As you navigate the complexities of relational data synchronization, keep in mind the nuances of each solution and the unique demands of your project. Whether opting for a well-established solution like Replication or embracing innovative approaches like Mirroring with Microsoft Fabric, make an informed decision based on your specific use case.
In conclusion, successful data synchronization is not a one-size-fits-all endeavor. By understanding the characteristics, advantages, and limitations of each solution, you empower yourself to make informed decisions that align with the dynamics of your data ecosystem. Explore further, stay updated on evolving technologies, and tailor your approach to meet the ever-evolving demands of your business.
You should remember that the technology world in general and in the cloud area in particular are constantly changing. The dynamic nature of data management and the importance of staying abreast of evolving technologies only emphasize that the reader should explore emerging solutions and best practices.
Microsoft Tech Community – Latest Blogs –Read More
Microsoft and Industry Leaders Enable RAN and Platform Programmability with Project Janus
Barcelona – February 26, 2024. Today at MWC 2024, Microsoft announced Project Janus, along with leaders across the telecommunications industry. Project Janus uses telco-grade cloud infrastructure compatible with O-RAN standards to draw on fine-grained telemetry from the radio access network (RAN), the edge cloud infrastructure, and other sources of data. This enables a communication service provider (CSP) to gain detailed monitoring and fast closed loop control of their RAN network. Janus has support and participation from CSPs such as Deutsche Telekom, and Vodafone; RAN and infrastructure providers CapGemini, Mavenir, and Intel Corporation; and RIC vendors and software innovators Juniper Networks, Aira Technologies, Amdocs, and Cohere Technologies.
“We know how vital the performance, security, and automation of the network is for CSPs, and going forward, more accurately optimizing complex networks,” said Yousef Khalidi, Corporate Vice President, Azure for Operators at Microsoft. “That’s why we’re excited to debut Project Janus alongside leading partners and supporters as an O-RAN compatible extension that makes RAN and platform even more programmable and optimized.”
Project Janus helps CSPs optimize RAN performance through visibility, analytics, AI, and closed loop control. To meet this objective, Microsoft and industry collaborators built a set of capabilities including RAN instrumentation tools that:
leverage the existing E2 O-RAN interface
update its service models to communicate with components of a CSP’s RAN and SMO architecture including the Distributed Unit (DU), Centralized Unit (CU), and RAN Intelligent Controller (RIC).
RAN, RIC, and xApp and rApp vendors are able to develop and use instrumentation tools to capture RAN data dynamically, and also combine them with platform data from cloud-based platforms hosting the RAN workloads.
This architecture enables several new use cases, such as precise analytics for anomaly detection and root cause analysis, interference detection, and optimizing other RAN performance metrics. The framework also enables new applications, such as fast vRAN power saving, failover, and live migration.
Project Janus will be available for everyone to include in their platform and network functions and will be supported natively by Microsoft’s Azure Operator Nexus platform.
To see specific use case examples, visit the “Unlock Operator Value with Programmable RAN & Platform” pod in the Microsoft booth at Mobile World Congress 2024 at 3H30 in Hall 3 during February 29-29, 2024 and check out www.microsoft.com/research/project/programmable-ran-platform/videos. Also read Mavenir, Microsoft and Intel Team for Real-Time Layer 1 vRAN Control white paper.
Telecommunications leaders are sharing support for the collaborative initiative:
Deutsche Telekom – “This initiative shows great promise to increase the pace of innovation and unlock new value through dynamic, customizable RAN data and analytics that can work within an O-RAN compliant framework. We look forward to seeing the participation by even more companies and developers in this burgeoning ecosystem.” – Petr Ledl, Vice President of Network Trials and Integration Lab and Chief Architect of Access Disaggregation program at Deutsche Telekom.
Vodafone – “The dynamic service models enabled by Project Janus are fully aligned with the vision of Open RAN in supporting the scale deployment of software-defined RAN. Access to the correct data at the right time and intelligent algorithms based on AI/ML capabilities will introduce significant performance and capacity benefits for all existing cellular networks and enable real autonomous ones.” – Francisco Martín Pignatelli, Head of Open RAN at Vodafone.
Hear from Microsoft Collaborators:
CapGemini – “CapGemini in collaboration with Microsoft has successfully demonstrated implementation of several use cases such as anomaly detection, energy savings and interference detection using Janus. These efforts have also demonstrated the benefits of being able to combine and reason over dynamic data from RAN, incremental to the predefined data types already available today, with dynamic data from the O-Cloud platform using Janus dynamic service models such as resolving key integration issues between RAN and platform as well as offering the power of leveraging AI/ML applications by developers to more precisely target areas of improvement for the RAN network.” – Rajat Kapoor, Vice President and Head of Software Frameworks at Capgemini.
Mavenir – “Improving RAN visibility and real-time control is essential to a CSP’s network performance and security, and it is Mavenir’s goal to support our customers with state-of-the-art observability. Data from our O-RAN-compliant DU/CU can be easily extracted dynamically and made available within our product management tools for tuning the operation of the Mavenir RAN. We demonstrated an advanced on-site debugging tool and customizable interference detection solution with Janus, which highlighted the flexibility of Janus to solve problems in real-time and improve system performance. With Janus, data from our Open RAN compliant DU can also be made available to an ecosystem of O-RAN focused application developers to provide insights and recommendations to the CSP to address and improve their network performance.” – Bejoy Pankajakshan, EVP, Chief Technology & Strategic Officer at Mavenir.
Intel Corporation – “With Intel FlexRAN reference architecture, Intel has been at the forefront of enabling the industry with virtualized, Open RAN to drive performance, flexibility and innovations, including AI. Microsoft’s Janus builds on FlexRAN’s software programmability to expose new data streams and application capabilities to the next generation of xApp developers, accelerating the adoption of AI in RAN networks to provide even more value to service providers”- Cristina Rodriguez, Vice President and General Manager of Wireless Access Network Division at Intel.
Juniper Networks – “Using the existing E2 O-RAN interface, Janus introduces the capability to bring more timely and customized RAN telemetry to Juniper Near-Real Time RIC. From this, we can enable xApp developers to use the incremental data to more precisely target areas of improvement for the performance and optimization of a RAN network.” – Constantine Polychronopoulos, Group VP of 5G and Telco Cloud at Juniper Networks.
Aira Technologies – “Our mission at Aira as an AI Defined Networking company is to enable the fully autonomous cellular RAN and our application of ML to wireless baseband processing is an industry first. Aira has showcased the use of Janus to collect and forward dynamic RAN data into our near-real time xApp where we apply leading-edge machine learning to drive better channel estimation and prediction to help maximize downlink throughput and range. We look forward to demonstrating, with Microsoft and the growing O-RAN ecosystem, even more innovation built on disaggregated and programmable networks.” – Anand Chandrasekher, Co-Founder and CEO at Aira Technologies.
Amdocs – “As a leading service provider and member of the ARI-5G Consortium, Amdocs is a key proponent of Open RAN and dedicated enabler of RAN intelligence and optimization and we do this today by offering among other things, Amdocs’ xApps such as the massive MIMO xApp. With Janus we look forward to leveraging dynamic service models with our network applications to further accelerate RAN performance and programmability for our CSP customers.” – Oleg Volpin, Division President Europe, Telefonica Global and Network Offering Division at Amdocs.
Cohere Technologies – “Cohere along with key operators and vendors is driving Multi-G ecosystem to enable co-existence of 4G, 5G and 6G and helping operators to do spectrum management in a seamless way. Janus’s dynamic infrastructure helps realize Multi-G’s dynamic infrastructure requirements and helps this vision.” – Prem Sankar Gopannan, Vice President of Product Architecture and Software Engineering.
Microsoft Tech Community – Latest Blogs –Read More
