Jump to content


All Activity

This stream auto-updates     

  1. Last week
  2. Hello, Did you look for those logs ? : - ContentTransferManager.log - DatatransferService.log - CAS.log
  3. Hello, Does anyone already faced this issue ? The user discovery method did discover new users in OUs but is not able to process the message to add them in DB:
  4. Hi, While testing the lock screen policy recently, I realised that it was N/A because my test device is running Windows 10 Pro. Given that it was purchased by work, it's covered under the Campus Agreement to upgrade to the Education edition. So, I could use the Edition Upgrade policy, but I'm a bit loathe to use the MAK key, given that the number of activations are limited, and on premise we have a KMS server. I've hunted the Microsoft documentations, but I've only found one reference to using the KMS keys - https://docs.microsoft.com/en-us/intune/edition-upgrade-configure-windows-10 But using the KMS key in itself doesn't seem to be enough; it needs to know where to activate (maybe with a PoSh script)? My question is, has anyone used Edition Upgrade with a KMS key? Or is it worth pursuing at all? Thanks! ... Alex ...
  5. WannaCry was a disaster that could have been prevented if people took notice. If you didn’t hear about it you must have been asleep, here is a refresher. After WannaCry, most businesses took notice and updated their operating systems, patched them and took measures to avoid a further outbreak. But today, May 14th, 2019, Microsoft has released information that warns of yet another WannaCry-like worm. Note: If you are using Windows 10, you are OK, you are not vulnerable to this CVE. If not, and if you are still on Windows 7 then start upgrading to Windows 10 by using the Inplace Upgrade Task Sequence I explain about here or if you cannot upgrade immediately, then patch Windows 7 to protect it from this vulnerability. Vulnerable in-support systems include Windows 7, Windows Server 2008 R2, and Windows Server 2008. Downloads for in-support versions of Windows can be found in the Microsoft Security Update Guide. Customers who use an in-support version of Windows and have automatic updates enabled are automatically protected. Out-of-support systems include Windows 2003 and Windows XP. If you are on an out-of-support version, the best way to address this vulnerability is to upgrade to the latest version of Windows. Even so, we are making fixes available for these out-of-support versions of Windows in KB4500705. If however you are running Windows XP, yes…. that old unsupported operating system then take warning ! Today, Microsoft has warned against the wormable capabilities from this CVE (critical Remote Code Execution vulnerability) and they blogged about what to do to avoid it happening to you. Read that blog post here: https://blogs.technet.microsoft.com/msrc/2019/05/14/prevent-a-worm-by-updating-remote-desktop-services-cve-2019-0708/ It’s very clear from their text that this is all about protecting customers from the next worm, so pay attention and if you have old operating systems that are in support and affected, then update immediately. Note: This is so serious that even Windows XP and Windows Server 2003 are getting updates from Microsoft for this vulnerability. You can download those updates from Microsoft Catalog here. https://support.microsoft.com/en-ca/help/4500705/customer-guidance-for-cve-2019-0708
  6. Altaro launches new solution incorporating secure storage and centralized backup management: Altaro Office 365 Backup Altaro Office 365 Backup enables customers to back up and restore all their company's Office 365 mailboxes on an annual subscription. It automatically backs up Office 365 mailboxes to a secure cloud backup location on Altaro's Microsoft Azure infrastructure and enables users to centrally manage and monitor their backups through a cloud-based management console. Altaro successfully entered the Office 365 backup market a few months ago with its solution that enables managed service providers (MSPs) to provide their customers with Office 365 backup, recovery and mailbox backup storage services. The channel-focused company is now also extending this offering for use by businesses and organizations who do not wish to subscribe to an MSP model, and to the IT consultants and resellers that service them. A central component of data protection strategies As part of their data protection strategy, it is crucial that businesses back up their Office 365 mailboxes: Microsoft does not back up Office 365 subscriber data, so companies risk losing critical data due to malicious or accidental incidents, such as mailbox deletion and malware attacks. Altaro's latest solution meets this need by providing customers with reliable and constant backup and recovery services for Office 365 mailboxes – emails, attachments, contacts and calendars – coupled with automatic storage to Altaro's Azure infrastructure. Convenient, fuss-free Office 365 backup and recovery For one all-inclusive annual or multi-year fee, Altaro Office 365 Backup customers receive backup and recovery services, backup storage services, access to the cloud console for centralized backups management, and outstanding 24/7 support from a team of experts. This means customers can avoid the headache and expense of setting up local storage infrastructure or software to save backups to. Additionally, thanks to the product automatically backing up the mailboxes several times per day, customers can literally set it and forget it. Combating Office 365 data loss risks "Many Office 365 subscribers wrongly assume that their data is backed up as part of the Microsoft package – but this is not the case, as Office 365 was not intended to be a data protection tool. This means several organizations out there are currently vulnerable to data loss risks," said David Vella, Altaro CEO. "This is where Altaro Office 365 Backup comes in, providing robust backup, recovery, and backup storage and management services that customers can rely on," he explained. "We've built on our backup expertise and proven track record in the industry to help set Office 365 subscribers' minds at rest." Free trial Resellers, consultants and organizations wishing to try the solution can do so for free and with no commitment for 30 days, by registering here.
  7. anyweb

    sccm 1802 help

    how can we suggest if it's a right design without knowing more about what you intend to do with this SCCM setup, how many clients will it manage, what type of clients, what locations, what operating systems...
  8. vipul

    sccm 1802 help

    I am planning to install SCCM 1802 on Azure cloud, my scenario will be like this install sccm management point on an Azure virtual machine ( OS will be Windows server 2016 datacenter 64 bit) Install SQL 2017 on Azure VM with OS windows 2016 datacenter edition 64 bit An SCCM distribution point on On premisses to communicate to the client. please suggest is this right design & also suggest should we need CMG for this. also, Certificate required for the same.
  9. Got a strange issue. SCCM 1606 SCEP is setup and has been working for a while. If we image a PC (Windows 10 1803), SCCM automatically deploys the SCEP policy and is successfully managed by SCCM. However, in some case we need to changed the policy to a standalone as the PC will not be able to communicate w/ the server. It's basically the same policy except it doesn't include our WSUS for definition updates and only go out to the internet. If we uninstall SCEP from Programs and Features and then run SCEPInstall.exe /policy <path>\StandAlonePolicy.xml right after imaging, it works fine. But if we wait too long and the SCEP client gets updated to a newer version, trying the same thing again fails w/ 0x80070002 "The system cannot find the file specified". I have tried just the SCEPInstall.exe w/out the policy and get the same error. At this point, I have not be able to get the PC to have a working SCEP client no matter what I do (aside from reimaging). Even SCCM is unable to reapply the default SCEP policy as the EndpointProtectionAgent.log shows the same error; Create Process Command line: "C:\WINDOWS\ccmsetup\SCEPInstall.exe" /s /q /policy "C:\WINDOWS\CCM\EPAMPolicy.xml". Detail error message is : [EppSetupResult] HRESULT=0x80070002 Description=Cannot complete the System Center Endpoint Protection installation. An error has prevented the System Center Endpoint Protection setup wizard from completing successfully. Please restart your computer and try again. Error code:0x80070002. The system cannot find the file specified. Maybe our process of changing the policy is incorrect so feel free to correct us. Thanks
  10. Earlier
  11. what version of SCCM, what version of MDT ? if you look at the boot image properties, is the option still checked ? have you tried redistributing the boot image to the dp's after the change also, are you 100% sure that this boot image is the one you were working on, you should see the package id when booting...
  12. have you looked at your client agent settings ? i would imagine that any setting configured in there is what makes the registry keys get set, perhaps you have some settings being applied which are not correct for these clients
  13. Configmgr client is setting this in the registry/local policy FillemptyContentURLS is set to 1 UpdateServiceUrlAlternate is set to http://localhost:8005 Deleting them makes it work. What are they for and why are they being set?
  14. it should only apply drivers from the package that windows deems necessary based on hardware found, you can verify this in the dism logs generated during windows setup
  15. Hi, I have recently installed 1902 and though I'd try the PXE Responder without WDS. It uninstalled WDS and the service for PXE Responder is running but whenever we try to build we get the following error "sccm PXE: recvfrom() failed for DHCP. 0x80072746.". I've since re-installed WDS and everything is working again. PXE: A0:8C:FD:D9:42:EB: 18058, GUID:11D3E3F7-385C-4446-BE52-200EEA465B33, SMBIOS ID is NOT a match, MAC Address is a match. SCCMPXE 09/05/2019 16:13:15 7996 (0x1F3C) PXE: A0:8C:FD:D9:42:EB: Using system record 18058, GUID:11D3E3F7-385C-4446-BE52-200EEA465B33. SCCMPXE 09/05/2019 16:13:15 7996 (0x1F3C) Operation: 2, Address type: 1, Address length: 6, Hop Count: 1, Transaction ID: 067b5c1f, Seconds since boot: 1024, Address: a0:8c:fd:d9:42:eb:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 172.27.22.72, Relay IP: 172.29.1.1 Options: 53, 1: 02 54, 4: ac 1b 16 48 97, 17: 00 e9 43 f4 97 47 7f 42 35 b9 45 ee aa 99 0e ba fe 60, 9: 50 58 45 43 6c 69 65 6e 74 SCCMPXE 09/05/2019 16:13:15 7996 (0x1F3C) PXE: Sending reply to 172.29.1.1, DHCP. SCCMPXE 09/05/2019 16:13:15 7996 (0x1F3C) PXE: recvfrom() failed for DHCP. 0x80072746. SCCMPXE 09/05/2019 16:13:15 9592 (0x2578)
  16. I found that article and thought I reviewed my configurations thoroughly but I didn't. I just now noticed this little guy, ▯, showing up in the publish path. Not sure how it got there but fixing that and rebooting allowed me to run the CRL command. Thanks! I probably would have kept overlooking that character without you pointing me back in that direction.
  17. check this out https://social.technet.microsoft.com/wiki/contents/articles/3081.ad-cs-error-the-directory-name-is-invalid-0x8007010b-win32http-267.aspx
  18. also, can you guys post screenshots of your issue(s) so we can try and figure out what the issue really is
  19. odd, i've just checked my current PKI lab and although my certs were expired (it's a lab and was shut down since march), using certutil -crl on the IssuingCA republished my certs and all is ok now. I've tested the PKI lab guides 3 separate times (I built 3 completely unique labs based on my own guides, eg: Lab #9, Lab #10, Lab #11) and all suceeded 100% as you can see below in my #11 lab... I would suggest you guys try again and verify each and every step as you go, also, take checkpoints (snapshots) between each part so that you can always go back if you make a mistake, lastly, the pki.windows-noob.com webserver URL, will of course be your 'own' url, and it must be reachable by the issuing CA and others or pkiview.msc will list a bunch of errors/failures. Troubleshooting Tip: in PKIview.msc, highlight an entry and click on the Refresh button in the ribbon, it should re-verify the highlighted item.
  20. they do but you still need to know if it's win7 or win10.... if you get time over teamviewer later i'd like to spend ten minutes with this to have a look
  21. Hi, If I apply drivers from a package during a OS deployment task sequence, will SCCM install all drivers within the package, even if the devices are not connected to the PC, or SCCM will only install drivers from the package, for the devices that are connected to the PC during the installation?
  22. Just want to throw it out there. The exact same behavior happened on my setup. Literally everything was healthy except for the Root CA LDAP CDP location #1.
  23. tried again with --> if (($OperatingSystem -eq "Microsoft Windows 10 Enterprise") -or ($OperatingSystem -eq "Microsoft Windows 10 Entreprise")) Result in the log file is --> This is not an approved operating system for the Windows 10 Ugprade, exiting with code 99, detected: 'Microsoft Windows 10 Entreprise' So even though the spelling is exactly the same, it still fails. It`s OK….Checking for version number only is fine for me. Computers understand numbers better anyway :-)
  24. Hello, Having an error getting the latest client to roll out via software updates Configuration Manager Client (5.00.8790.1007) -Error 0x80d05001 How can I find the package on the distribution points to redistribute it as I think this could be the issue? Thanks
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×
×
  • Create New...